Module ranking for a modular inbox

ABSTRACT

Exemplary embodiments relate to improvements in the design of a messaging inbox. The inbox may display different units or “modules” for providing a user with quick access to different inbox functionalities. Content may be ranked and ordered within a module, and modules may be ranked and ordered with respect to each other. Inter-module ranking may be based on elements such as individual activity and the activity of the messaging service&#39;s user base, the value of the module to the messaging service, and offline models. Intra-module ranking may be defined by individual modules (e.g., based on recency, importance to user, affinity, etc.). Intra-module ranking may affect inter-module ranking, such as when individual content in a low-rated module is particularly exciting or pertinent (causing the entire module to receive a higher inter-module ranking).

BACKGROUND

Messaging systems, such as instant messaging systems and short messageservice (“SMS”) systems, allow users to communicate with each other byexchanging messages. Messaging services may also provide capabilitiesbeyond exchanging messages, but in many cases the user may not be awareof the additional capabilities or how to use them. In some situations,the additional capabilities may be relatively difficult to locate in amessaging application, or their use may be non-intuitive. As a result,these additional capabilities may be underutilized. Moreover, users ofthe messaging service who might be relatively active users if they wereaware of the additional capabilities may instead become less active.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A depicts an exemplary messaging interface including several typesof individual and group messages;

FIG. 1B depicts an exemplary message composition interface;

FIG. 1C depicts an example of selecting a recipient of a message in amessaging interface;

FIG. 1D depicts an example of selecting a group of recipients of amessage in a messaging interface.

FIG. 2A depicts an exemplary interface for a messaging inbox including afirst portion displaying a first set of messages, a second portiondisplaying one or more modules, and a third portion displaying a secondset of messages;

FIG. 2B depicts an exemplary interface for a messaging inbox in which asecond set of messages is displayed in the first portion of theinterface including the first set of messages;

FIG. 2C depicts an example of a top contacts module;

FIG. 2D depicts an example of a people/states module;

FIG. 2E depicts an example of a new behavior module;

FIG. 2F depicts an example of a live videos module;

FIG. 2G depicts an example of an events module;

FIG. 2H depicts an example of a businesses module;

FIG. 2I depicts an example of a messaging stickers module;

FIG. 2J depicts an example of a wireless network finder module;

FIG. 2K depicts an example of a transportation services module;

FIG. 3 is a flowchart depicting an exemplary process for displaying aninbox interface including one or more modules;

FIG. 4A depicts an example of a sharing module for sharing localcontent;

FIG. 4B depicts an example of a sharing module for sharing socialnetworking content;

FIG. 4C depicts an exemplary interface for selecting content to beshared;

FIG. 4D depicts an exemplary interface for selecting a group ofrecipients to receive the content selected in FIG. 4C;

FIG. 4E depicts an exemplary interface for confirming the sending of thecontent to the recipients;

FIG. 4F depicts an exemplary inbox after receiving the content shared inFIGS. 4C-4E

FIG. 4G is a flowchart depicting an exemplary process for sharingcontent from a module;

FIG. 5A depicts an example of a promotional material module;

FIG. 5B depicts an example of promotional material integrated intonon-promotional material module;

FIG. 5C depicts an example of a message generated in response tointeracting with promotional material;

FIG. 5D is a flowchart depicting an exemplary process for providingpromotional content in a module;

FIG. 6 is a flowchart depicting an exemplary process for determining atransition point between a first group of messages and a set of one ormore modules;

FIG. 7A is a block diagram providing an overview of a module rankingframework;

FIG. 7B is a flowchart depicting an exemplary process for determining aninter-module rank;

FIG. 7C is a flowchart depicting an exemplary process for determining anintra-module rank;

FIG. 8A is a block diagram providing an overview of a system includingan exemplary centralized messaging service;

FIG. 8B is a block diagram providing an overview of a system includingan exemplary distributed messaging service;

FIG. 8C depicts the social networking graph of FIGS. 8A-8B in moredetail;

FIG. 9 is a block diagram depicting an example of a system for amessaging service;

FIG. 10 is a block diagram illustrating an exemplary computing devicesuitable for use with exemplary embodiments;

FIG. 11 depicts an exemplary communication architecture; and

FIG. 12 is a block diagram depicting an exemplary multicarriercommunications device.

DETAILED DESCRIPTION

Messaging applications may provide an inbox that allows a user to readand send messages. However, a messaging application may provideadditional functionality beyond reading and sending messages, such asplaying games, sending money to a friend, viewing which other users areonline in order to spur a conversation, etc. If these additionalfunctions are hidden in menus or accessed through special commands orgestures, many users will rarely or never use them. The users may notknow that this functionality exists, or accessing the functionality mayprove too cumbersome to encourage regular use. Because thisfunctionality can spur increased use of the messaging application,administrators of the messaging service way wish to encourage its use.

In a messaging inbox displaying messages, it is often the case that somemessages are more important or valuable to a user than others. Forexample, it may be highly likely that a user will wish to access recentmessages and unread messages, whereas relatively stale messages ormessages that have been previously read are less likely to be accessed.

According to exemplary embodiments, these insights are combined toprovide a modular inbox that encourages use of the messaging service'sfull functionality, while also providing ready access to the user's mostimportant or valuable messages. In the modular inbox, the inbox may bedivided into different inbox units or modules. The modules may provide auser with quick and convenient access to different inbox functionalitiesthat the user might not otherwise be aware of (or inclined to use on aregular basis).

After a number of messages are shown in the inbox's initial display, themessages end and are replaced with modules. The number of messages todisplay before switching to modules (referred to herein as a messagingcliff) is determined based on a minimum threshold and a dynamic maximumthreshold that can differ from user-to-user and based on the context(e.g., the time of day).

The point where the inbox transitions from the recent messages to themodules (the messaging cliff) may be determined statically ordynamically. A static determination may involve transitioning to themodules after a predetermined number of recent messages. A dynamicdetermination may be made based on, for example, selecting a number ofmessages to display that falls within a minimum number of messages and amaximum number of messages. The minimum may be, for example, 4-8messages and may be based on a predetermined minimum message threshold.The maximum number of messages may be dynamic, and may be based on thecurrent time of day, the number of message threads in which the user isparticipating in an active conversation, or the number of unreadmessages in the user's inbox (e.g., the cliff may be set to display allunread messages within a certain time frame, which may include gapswhere read messages have been filtered out). The maximum number ofmessages displayed may be different for different users. For example, apower user may receive a large number of messages over a short timeframe. Such a user might see messages only from the very recent past butmight have a higher threshold for the number of messages to display. Aninfrequent user, on the other hand, might see fewer messages over alonger time frame. User activity may be determined based on historicalusage of the messaging application or messaging service.

The modules section of the inbox differs from the message displaysection of the inbox in that the modules are primarily configured forfunctionality other than the displaying of messages or message threads.Modules may provide different kinds of functionality, such as showingactive users, suggesting new activities, or making it easy to sharecontent from a device (e.g., through the device's camera roll or photoalbum), a social networking service, or another source. The modules mayinclude modules for sharable articles/videos/pictures that allow a userto select content to be provided to other messaging service users.Modules can also include, or can be, advertisements.

Further embodiments provide modules relating to the sharing of contentfrom a social networking service associated with the messaging service.For example, some modules may allow a user to share articles, videos, orpictures from the social networking service. Exemplary interfacessimplify the sharing procedure by providing content recommendations,which may be retrieved from the social networking service based onconsumption information. Alternatively or in addition, the content maybe retrieved from a location outside the social networking service, orfrom multiple sites.

Content items within modules can be ranked to determine whichintra-module order to display the content items. The content may beranked based on a number of metrics, such as recency of access,interaction time, and/or an enjoyment metric personalized to a givenuser. The intra-module content ranking scheme may be defined on amodule-by-module basis. Content may be displayed in the sharing modulebased on the rank.

In addition to (or alternatively from) ranking the content within amodule, the modules may also be ranked against each other in order todetermine which order to show the modules. Inter-module ranking may bedetermined based on ranking metrics, such as the user's estimatedinterest in the module, the estimated interest in the module among auser base of the messaging service, and a value of displaying the moduleto the messaging service or an associate of the messaging service.Inter-module ranking may be determined at a server communicating with aclient device, although the inter-module ranking scheme may also beextensible with offline models.

The intra-module content ranking may be used to affect the inter-moduleranking. For example, if a particular content item in a low-rankedmodule is determined to be particularly pertinent or exciting (e.g., anarticle is currently being viewed by a large number of people on asocial network), then this may cause the content item's module to beelevated in the inter-module ranking. In some circumstances, the modulemay even be elevated above the messages displayed in the first sectionof the inbox.

When sharing content, the module may suggest a group of recommendedrecipients. The group may include members selected based on the content(e.g., who is considered the most likely to enjoy the content) and/ormetrics based on users with whom the sharing user has historicallyshared similar content.

When sharing local or social networking media, exemplary embodimentsprovide simple low-friction ways to share the material. In general, thesystem may provide an interface displaying content recommendations and alist of suggested users with whom the content may be shared. Uponselecting the content and a list of target users, the original user maysimply press send, and the messaging service will automatically generatesuitable messages and/or message threads to share the content.

Still further, some modules may be used to deliver promotionalmaterials. Promotional material may be in the form of promotionalcontent items, such as individual offers or advertisements. Thepromotional content items may be presented in a dedicated module (e.g.,a promotional materials module), and/or may be integrated into othermodules (e.g., providing a promotional content item among the shareablearticles in an articles module). In some embodiments, a business maypurchase a higher ranking for their promotional content item to allowthe promotional content item to be displayed earlier in the list ofmodules or within a given module.

Interacting with the promotional content items may cause a new messageor thread to be delivered to the user's inbox. Such a message mayinclude a code that offers a discount when scanned in a retail location.The messages and/or promotional content items may be generated based onproximity. In one example, promotional content items may be displayedbased on a user's affinity, and interacting with a promotional contentitem may allow a user to claim an offer from a provider. When the user'sdevice is identified at a location proximate to a retail location forthe provider, the user may be sent a message prompting the user to enterthe retail location and scan the code to receive a discount.

In some embodiments, sponsored promotional content items (e.g.,advertisements) may be distinguished from discount offers, which aregenerally perceived to be purely beneficial and thus may be bettertolerated by users in certain circumstances. Different types ofpromotional content items may be prompted in different ways, andinteracting with different types of promotional content items mayproduce different results. For example, purely sponsored promotionalcontent items may be displayed in an advertising-specific module,whereas discount items may be presented among other content items in adifferent module. In some cases, purely sponsored promotional contentitems may be displayed among other content items (e.g., when the user isdetermined to be in a location proximate to a provider of thepromotional content item). In another example, interacting with adiscount offer may cause an interface to be presented allowing the userto share the discount offer with their friends (e.g., to encourage thefriends to go to a coffee shop together), whereas interacting with apromotional content item containing an advertisement might open amessage thread with the sponsor of the promotional content item.

After scrolling through the recent messages and reaching the cliff, theuser may scroll through the modules. When the available modules areexhausted (or after displaying a predetermined or dynamically determinednumber of modules), the inbox may transition back to older unreadmessages. Alternatively or in addition, older or unread threads may becollapsed into the top section, before the cliff.

As an aid to understanding, a series of examples will first be presentedbefore detailed descriptions of the underlying implementations aredescribed. It is noted that these examples are intended to beillustrative only and that the present invention is not limited to theembodiments shown.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. However,the novel embodiments can be practiced without these specific details.In other instances, well known structures and devices are shown in blockdiagram form in order to facilitate a description thereof. The intentionis to cover all modifications, equivalents, and alternatives consistentwith the claimed subject matter.

In the Figures and the accompanying description, the designations “a”and “b” and “c” (and similar designators) are intended to be variablesrepresenting any positive integer. Thus, for example, if animplementation sets a value for a=5, then a complete set of components122 illustrated as components 122-1 through 122-a may include components122-1, 122-2, 122-3, 122-4, and 122-5. The embodiments are not limitedin this context.

Messaging Overview

A general overview of messaging techniques is now described.

Users may interact with a messaging system through a client application.FIG. 1A depicts an example of a client application displaying amessaging interface 100. The messaging interface 100 of FIG. 1A shows anexemplary summary screen that provides an overview of messages recentlysent to (or by) the user of the client application.

Messaging systems may support a variety of different types of messages.For example, the messaging interface 100 includes a summary of aone-to-one (or individual) message 102. A one-to-one message is amessage exchanged between two entities, so that only the two entitiescan see and participate in the conversation. For example, in theone-to-one message 102, the current user (Jack Doe) recently received amessage from his wife, Jane Doe. The other participant in theconversation is indicated in the interface 100 using an identifier 104(including a name and profile picture, in this example). Only Jack andJane participate in the conversation, and only Jack and Jane can viewthe conversation.

Another message type supported by the messaging system is a groupconversation. In a group conversation, multiple users see andparticipate in the conversation. FIG. 1A depicts an exemplary summary ofa group conversation 106. In the summary of the group conversation 106,each of the other users participating in the conversation is indicatedby respective identifiers 108. In this case, the identifiers include thenames or handles of the other users participating in the groupconversation, and an icon to indicate that the conversation is a groupconversation. For example, in this case the current user (Jack) isparticipating in a conversation with his friends Ben and Alex. Jack,Ben, and Alex can each see all of the messages in the conversation(regardless of who sent the message) and can send messages to the group.

Another type of message supported by the messaging system is a messagebetween one or more users and an organization (such as a business) orevent. For example, FIG. 1A shows an event message 110 sent by thecurrent user (Jack) to the page of an event being organized through asocial network. The identifier 112 identifies the name of the event, andan icon is presented identifying this particular event is a concert. Inan event message 110, all participants in the event (as a participant isdefined, e.g., by the event's social networking page) can view and sendevent messages 110. Participants may include, for example, peopleattending the event, fans of the event that have signed up with theevent's page to receive messages about the event, event organizers, etc.

By selecting an existing message summary 102, 106, 110, the user canview messages in an existing conversation and add new messages to theconversation. Moreover, the interface 100 includes interface elements114 allowing the user to create a new message.

For example, FIG. 1B depicts an interface 116 displayed by the messagingclient application in response to receiving a selection of the “compose”interface element 114. A “new message” window is displayed in theinterface 116. The new message window includes a recipient field 118 forallowing the user to manually enter identifiers for one or morerecipients. If available, the user's contacts list 120 may also bedisplayed in the interface 116 in order to simplify the selection of therecipients.

In the example of FIG. 1C, the user has entered the identifier of arecipient in the recipient field 118. In order to indicate therecipient's inclusion in the recipients list, a selection indication 122is displayed on the recipient's icon in the contacts list 120.

It is possible to select more than recipient in the interface 116 inorder to create a group message, e.g. by manually adding multiplerecipients in the recipient filed 118, selecting multiple contacts inthe contacts list 120, or a combination of methods. FIG. 1D depicts anexample of such a group selection.

This brief summary is intended to serve as a non-limiting introductionto the concepts discussed in more detail below, in connection with FIGS.2-8. However, before discussing further exemplary embodiments, a briefnote on data privacy is first provided. A more detailed description ofprivacy settings and authentication will be addressed in connection withthe following Figures.

A Note on Data Privacy

Some embodiments described herein make use of training data or metricsthat may include information voluntarily provided by one or more users.In such embodiments, data privacy may be protected in a number of ways.

For example, the user may be required to opt in to any data collectionbefore user data is collected or used. The user may also be providedwith the opportunity to opt out of any data collection. Before opting into data collection, the user may be provided with a description of theways in which the data will be used, how long the data will be retained,and the safeguards that are in place to protect the data fromdisclosure.

Any information identifying the user from which the data was collectedmay be purged or disassociated from the data. In the event that anyidentifying information needs to be retained (e.g., to meet regulatoryrequirements), the user may be informed of the collection of theidentifying information, the uses that will be made of the identifyinginformation, and the amount of time that the identifying informationwill be retained. Information specifically identifying the user may beremoved and may be replaced with, for example, a generic identificationnumber or other non-specific form of identification.

Once collected, the data may be stored in a secure data storage locationthat includes safeguards to prevent unauthorized access to the data. Thedata may be stored in an encrypted format. Identifying informationand/or non-identifying information may be purged from the data storageafter a predetermined period of time.

Although particular privacy protection techniques are described hereinfor purposes of illustration, one of ordinary skill in the art willrecognize that privacy protected in other manners as well. Furtherdetails regarding data privacy are discussed below in the sectiondescribing network embodiments.

Assuming a user's privacy conditions are met, exemplary embodiments maybe deployed in a wide variety of messaging systems, including messagingin a social network or on a mobile device (e.g., through a messagingclient application or via short message service), among otherpossibilities. An overview of a messaging system is now provided

Modular Inbox Overview

FIG. 2A depicts an exemplary interface 200 for a messaging inbox. Theinterface includes a first portion 202 for displaying a first set ofmessages 204, a second portion 206 displaying one or more modules 208,and a third portion 210 displaying a second set of messages 212.

Although FIG. 2A depicts each of the first portion 202, the secondportion 206, and the third portion 208 together on a single screen ofthe device, any or all of the interface portions may extend to or beyonda single device screen. The user may navigate through the interface 200,for example by scrolling.

The first set of messages 204 may be the most relevant or recentmessages, whereas the second set of messages 212 may be less relevant orrecent messages. The transition point between the first set of messages204 and the second set of messages 212 is referred to herein as amessage cliff. Techniques for determining which messages to include inthe first set of messages 204, and which to include in the second set ofmessages 212, are covered in detail in the section below addressing TheCliff.

Scrolling through the interface 200 may cause the interface 200 toexpose or display the first portion 202, the second portion 206, and thethird portion 210, respectively. For example, the display may firstrender the first portion 202 of the interface 200. If the messages 204of the first portion 202 do not occupy all of the display spaceavailable to the interface 200, then at least a part of the secondportion 206 may also be displayed (as much as will fit in the space leftover after the first portion 202 is displayed). If the messages 204 ofthe first portion 202 occupy more space than is immediately available tothe interface 200, then scrolling through the interface 200 may causeadditional messages in the first set of messages 204 to be displayed,until the user reaches the messaging cliff. If the user continues toscroll after reaching the messaging cliff, then the second portion 206including the modules 208 may be displayed. The user may continue toscroll through the modules 208 until the available modules areexhausted. At this point, the interface 200 may begin to display thethird portion 210 including the second set of messages 212.

In the example of FIG. 2A, the messaging inbox displays messages up to acertain point (the first set of messages 204), then modules 208, andthen the second set of the user's messages 212 (in the third portion 210of the interface 200). As an alternative, or in addition to, thisapproach, some or all of the second set of messages 212 (messagesfalling after the messaging cliff) may be collapsed into the firstportion 202 of the interface 200.

For example, FIG. 2B depicts an exemplary interface 214 for a messaginginbox in which a second set of messages is displayable in the firstportion 202 of the interface 200, which also includes the first set ofmessages 204. In the interface 214, the second set of messages may beinitially hidden behind a collapsible heading 216 having an expandableinterface element 218. Interacting with the expandable interface element218 may cause the second set of messages 204 to be displayed.

As further depicted in FIG. 2B, in addition to scrolling through theinterface 200 as a whole, individual modules 208 may also be scrollable.The modules 208 may present a predetermined amount of content oroptions. For example, a videos module 220 may display a number of videosfrom a social networking service that the system considers the currentuser to be most likely to share with friends. If the system determinesthat the amount of content can fit on the display of the user's device(e.g., based on the screen width and resolution available to theinterface 200), then the content may be entirely displayed within thewidth of the interface, in a section reserved for the module 208.

On the other hand, if the amount of content does not entirely fit on thedisplay (or if the module 208 allows for a potentially unlimited oramount of content), then the system may provide options for allowing theuser to scroll through the videos module 220. The system may present anoption to scroll horizontally through the content (e.g., by allowing auser to gesture on a touch display with a left- or right-swipe),vertically through the content (e.g., by allowing a user to gesture onthe touch display with an up- or down-swipe within an area reserved forthe module), or both. In the depicted example, a horizontal scroll bar222 shows the user's progress through the available content.

Exemplary Modules

The second portion 206 of the interface 200 may include multipledifferent sections providing different types of modules 208. Exemplarymodules 208 are discussed below, although it is contemplated thatadditional types of modules may also be used. Exemplary embodiments maydisplay some or all of the different types of modules 208 in the secondportion 206 of the interface 200. The modules 208 to be displayed may beselected based on the user's sharing history or interactions with asocial networking service; those modules that the social networkingservice considers are most likely to be useful to the user may beselected for display.

FIG. 2C depicts an example of a top contacts module 224. The topcontacts module 224 may include a list of top contacts 226 from themessaging inbox owner's contacts list. The top contacts 226 may beselected from the contacts list based on, for example, the inbox owner'smessaging history (e.g., which users the inbox owner has messaged mostfrequently, most recently, at certain times of the day, etc.), and/orother metrics such as an affinity of the inbox owner for the contact, aproximity of the contact to the inbox owner, or context-sensitiveinformation such as a current or future change in location.

For example, if an out-of-town contact is traveling to the inbox owner'slocation, then the out-of-town contact may be displayed in the topcontacts module 224, even if they would not otherwise be included basedon other metrics. In another embodiment, the contacts may be selectedbased on properties of the contact (such as whether it is the contact'sbirthday). In yet another example, the system may add contacts to thelist if the contact has not been messaged by the inbox owner for morethan a predetermined period of time, particularly if the contact wassomeone that the message owner previously contacted often (e.g., toencourage the inbox owner to message the contact). Explanatoryinformation (e.g., “User X will be visiting City Y from Date A to DateB”) may be displayed in the top contacts module 224.

A predetermined number of top contacts 226 may be selected for displayin the top contacts module 220. Optionally, the predetermined number maybe user-configurable so that the user may specify how many top contactsto display. If the number of contacts displayed in the top contactsmodule 224 is too great to fit within the space reserved for the topcontacts module 224 on the display, then the top contacts module 224 maybe scrollable (e.g., with a horizontal scroll).

FIG. 2D depicts an example of a people/states module 228. Thepeople/states module may display a list of the user's contacts whosatisfy a condition that the contact be in one or more selected states.For example, the people/states module 228 may include a list of contacts230 that are currently online, or who have recently participated in aconversation. The people/states module 228 may include an indicator 232that indicates the current state of the associated contact 230. In thedepicted example, the indicator 232 is a color-coded dot that changescolor to reflect if the contact 230 is online or away.

The list of contacts in the people/states module 228 may be dynamicallyupdated as contacts in the user's contacts list change their states,with contacts being added or removed from the people/states module. Thepeople/states module may be configurable to allow the user to select howmany contacts should be displayed in the people/states module, and inwhich state(s) the user is interested. If the people/states module 228is configured to display a specific number of contacts that is less thanthe total number of contacts that match the selected states, then thepeople/states module 228 may apply one or more relevancy metrics todetermine which contacts to display (e.g., contacts most recentlymessaged, contacts messaged at the highest frequency, etc.). Therelevancy metrics may include the metrics described above in connectionwith the top contacts module.

FIG. 2E depicts an example of a new behavior module 236. The newbehavior module 236 presents a list of behaviors or activities that theinbox owner could engage in on the messaging service, but for which theinbox owner has not (or has not recently) engaged. In the depictedexample, the user is presented with the content option 238-1 to chatwith a bot representing a company that the user likes or is predicted tolike.

The new behavior module 236 may also or alternatively suggest behaviorsin which the user does engage in some contexts, and for which themessaging service determines the user would be likely to engage ifpresented with the opportunity. For example, the user may havepreviously joined an interest group (e.g., “Rock Climbers ofSpringfield”), and the messaging service may determine that the userwould be likely to want to join a related group. In the depictedexample, the user is presented with a content option 238-2 to join the“Rock Breakers” group, representing another group of local rockclimbers.

In a further example, the user may have previously participated inhangouts or online gatherings; when a celebrity or public figure beginsa new hangout or gathering, the user may be presented with an option238-3 to join the gathering in the new behaviors module 236.

In another example, if new functionality is added to the messagingservice, then the new behavior module 236 may suggest that the inboxowner try the new functionality. One example of new behavior may beengaging in a video conversation—if the inbox owner has not previouslyengaged in a video conversation, but instead has always engaged in textmessages, then the new behavior module 236 may suggest that the inboxowner initiate a video call with another user.

FIG. 2F depicts an example of a live videos module 240. The live videosmodule 240 may present content options 242-1, 242-2 representing livevideo streams currently being transmitted by other users of themessaging service (or an associated social networking service). The livevideos module 240 may also present a content option 242-3 for allowingthe inbox owner to create a live video stream from their device.

FIG. 2G depicts an example of an events module 244. The events module244 may display a list of upcoming events 246 that the inbox ownerand/or the inbox owner's contacts are scheduled to attend. Alternativelyor in addition, the events module 244 may display a list of events 246in which the messaging service or social networking service havedetermined the inbox owner may be interested (e.g., based on the inboxowner's interests as indicated through the inbox owner's interactions ona social network, or based on the interests of the inbox owner'scontacts).

FIG. 2H depicts an example of a businesses module 248. The businessesmodule 248 may display a list of businesses 250 that the inbox ownerand/or the inbox owner's contacts have previously interacted.Alternatively or in addition, the businesses module 248 may display alist of business 250 in which the messaging service or social networkingservice have determined the inbox owner may be interested (e.g., basedon the inbox owner's interests as indicated through the inbox owner'sinteractions on a social network, or based on the interests of the inboxowner's contacts).

FIG. 2I depicts an example of a messaging stickers module 252. Themessaging service may allow the inbox owner to add graphics referred toas stickers to a message. These stickers may be downloaded from themessaging service, a social networking service, or another site. Thestickers module 252 may display a list of stickers 254 for which theinbox owner may have an interest. The inbox owner may interact with thestickers module 252 in order to download or flag stickers for use infuture messages. Upon selecting one or more of the stickers 254-i, theselected stickers may be downloaded and added to the user's locallibrary for future use.

FIG. 2J depicts an example of a wireless network finder module 256. Thewireless network finder module 256 may display a list of availablewireless networks 258 in proximity to the device of the inbox owner. Thewireless network finder module 256 may also display information aboutthe networks, such as the network name, the entity that provides ormanages the network, wireless signal strength, and whether and how thenetwork is secured. The inbox owner may select one of the wirelessnetworks through the wireless network finder module 256 in order toconnect to the wireless network.

FIG. 2K depicts an example of a transportation services module 260. Thetransportation services module 260 presents options for allowing theinbox owner to secure transportation, either immediately or at ascheduled time. The transportation services module 260 may display alist of transportation services 262 that are available in an areaproximate to the inbox owner (as determined, for example, by thelocation of the inbox owner's mobile device). The transportationservices may include, for example, taxi services, ride sharing services,public transportation, etc. The transportation services module 260 mayconnect to an application on the user's device, or to an internet site,for securing the transportation services. The transportation servicesmodule 260 may connect to a social networking page associated with atransportation service and may allow the user to communicate with theride sharing service's page (e.g., through bot interaction). Thetransportation services module 260 may, alternatively or in addition,display a calendar allowing transportation services to be scheduled fora future time.

Any or all of the above-described modules may be displayed in the inboxinterface (as well as additional modules described below). FIG. 3 is aflowchart depicting an exemplary process 300 for displaying an inboxinterface including one or more modules.

At block 302, a messaging application may receive an instruction todisplay an inbox interface for a messaging service associated with themessaging application. Block 302 may occur, for example, in response tostarting up the messaging application or in response to receiving aninstruction to access a home screen or inbox screen in the messagingapplication.

At block 304, the inbox interface may be generated and a first set ofmessages may be displayed in a first portion of the inbox interface. Thefirst portion of the inbox interface may provide thread displayfunctionality, in which message threads are displayed. The messagethreads may be summarized in the first portion of the inbox interface(e.g., by displaying a thread's most recent message, or a representativemessage of the thread, and/or a list of participants in the thread).Interacting with one of the message threads may cause the message threadto be expanded so that an exchange between two or more threadparticipants may be viewed.

In some embodiments, the first portion of the interface may be providedas a module specifically dedicated to message or thread displayfunctionality.

The first set of messages displayed in the first portion of the inboxinterface may include a subset of the totality of the threads ormessages available to the inbox owner, as determined based on amessaging cliff (discussed in more detail below). For example, the firstset of messages may include a set of unread messages or a set of recentmessages received within a predetermined amount of time.

In some embodiments, messages that are not selected for inclusion in thefirst set of messages may be collapsed into a message header andpresented, e.g., at the end of the first set of messages.

At block 306, the inbox interface may receive an instruction to navigatepast the first portion of the inbox interface. For example, themessaging application may register a gesture on a touch screencorresponding to a scrolling gesture, where scrolling the interface inaccordance with the gesture would cause the interface to scroll beyondthe final message or message thread in the first set of messages.Scrolling or navigation may be achieved in other ways as well, such asby interacting with a pointing device (e.g., a computer mouse), voicecommands, etc.

At block 308, the messaging application may cause a second portion ofthe inbox interface to be displayed. The second portion may include oneor more modules, where the modules of the second portion provide accessto functionality that is different from the message or thread displayfunctionality of the first portion of the inbox interface. As the inboxinterface is scrolled through, the second portion of the inbox interfacemay incrementally or immediately replace the first portion of the inboxinterface as the inbox interface is scrolled.

A list of the modules to display may be retrieved from a messagingserver. The list may include a set of identifiers associated with eachmodule to be displayed. Optionally, an entry in the list associated witheach module may include further information, such as a type of themodule, metadata such as a name of the module to be displayed, andoptionally may include content items to be displayed. The content itemsreturned with the list of the modules may be a null (empty) set, inwhich case the module may determine which content to display, eitherbased on local content on the client device or remote content on aserver associated with the module.

The messaging server may determine a subset of available modules toassign to the user (e.g., based on the user's predicted affinity for themodules) and may provide the list of modules to a client device runningthe inbox owner's messaging application.

The ordering of the modules in the second portion of the inbox interfacemay be determined by an inter-module ranking, as discussed in moredetail below. In some cases, a module in the set of modules may bedetermined to be highly relevant, which may cause the module to beelevated in the inter-module ranking. In some embodiments, if it isdetermined that one of the modules in the set of modules is particularlyrelevant (e.g., above a certain relevancy threshold), then the modulemay be elevated even above the first portion of the interface (e.g., sothat the module is displayed before the messages or message threads).For example, if a particular live video is being viewed by a significantnumber of the contacts of the inbox owner, then the live videos modulemay be elevated above the messages of the first portion of theinterface.

The content within the modules may be retrieved from the messagingserver associated with the messaging service. Alternatively or inaddition, the content may be retrieved from separate servers associatedwith each module (e.g., each module may independently define and fetchits own content).

At block 310, the inbox interface may receive an instruction to navigatepast the second portion of the inbox interface. For example, themessaging application may register a gesture on a touch screencorresponding to a scrolling gesture, where scrolling the interface inaccordance with the gesture would cause the interface to scroll beyond afinal module of the set of modules in the second portion of theinterface. Scrolling or navigation may be achieved in other ways aswell, such as by interacting with a pointing device (e.g., a computermouse), voice commands, etc.

At block 312, the messaging application may optionally cause a secondset of messages or message threads to be displayed in a third portion ofthe inbox interface. The third portion may be displayed after the secondportion, and may incrementally or immediately replace the second portionof the inbox interface as the inbox interface is scrolled. The secondset may include messages or message threads that were not flagged forinclusion in the first set of messages.

Alternatively or in addition, some or all of the second set of messagesor message threads may be collapsed in the first interface portion, asdescribed above.

Sharables Modules

A number of module types have been discussed above. In addition to thesemodules, a particular type of module configured to share local or socialnetworking content may also be provided. Sharables modules are describedin detail with reference to FIGS. 4A-4G.

FIG. 4A depicts an example of a local sharing module 402 for sharinglocal content. A number of local content items 404 may be displayed inthe sharing module 402. The local content items 404 may be, for example,photos or videos from a local device on which the messaging applicationis running.

The local sharing module 402 may display a predetermined or dynamicallydetermined number of local content items 404 on the display. More localcontent items 404 may be accessible, for example using a horizontalscrolling technique or through an additional menu 406. Activation of themenu 406 may, for example, cause the local sharing module 402 to presentan interface into the local storage of the device. The messagingapplication may, for example, access the photo album of the local deviceand suggest photos or videos that the inbox owner may be interested insharing with their contacts.

FIG. 4B depicts an example of a social media sharing module 408 forsharing social networking content. The social media sharing module 408may retrieve content items 410 associated with the inbox owner from asocial networking service. For example, the content items 410 mayinclude media that has been uploaded by the inbox owner to the socialnetworking service, media that the inbox owner has interacted withthrough the social networking service (e.g., content on which the inboxowner has commented, liked, etc.), or media that the social networkingservice determines that the inbox owner is likely to appreciate orenjoy. The content items 410 may include, for example, videos, pictures(e.g., GIFs), articles, etc. that have been uploaded to, or otherwiseaccessed from, the social networking service.

Additional content items 410 may be available through a horizontalscrolling technique. Alternatively or in addition, a menu 412 may beprovided for displaying additional content items 410. Activation of themenu 412 may, for example, cause the social media sharing module 408 topresent an interface into the social networking service and displayadditional content items 410 available through the social networkingservice.

FIG. 4C depicts an exemplary interface 414 for selecting content to beshared. The content may be local content as shown in the local sharingmodule 402 or content from a social networking service as shown in thesocial media sharing module 408. In the depicted example, the contentitems 416 in the interface 414 represent articles available on a socialnetworking service.

As shown in FIG. 4C, one or more of the content items 416 may beselected. The selected content items may be identified using anidentifier 418, such as a checkmark in this example. Once one or more ofthe content items 416 are selected, a recipients interface may bedisplayed, as shown in FIG. 4D.

FIG. 4D depicts an exemplary interface 420 for selecting a group ofrecipients 422 to receive the content selected in FIG. 4C. Therecipients 422 displayed in the interface 420 may include usersconnected to or associated with the inbox owner through a socialnetworking service or through the messaging service. For example, therecipients 422 may include recipients with whom the inbox owner hasrecently shared content items, or whom the inbox owner has recentlymessaged. The recipients 422 may be selected, at least in part, based onan identity of the content items 416 selected for sharing. For example,the social networking service may identify a subset of the inbox owner'scontacts or friends on the social networking service who (based on theirown content interaction history) the social networking servicedetermines are likely to enjoy or appreciate the content items 416. Toaccomplish this, the social networking service may consult a socialgraph, as described in more detail below.

Upon selecting one or more of the recipients 422, an indication 424(such as a check box, in this example) may be displayed to indicatewhich recipients 422 have been selected. The messaging application maythen display an interface for confirming the sending of the content tothe recipients, such as the exemplary interface 426 depicted in FIG. 4E.

The interface 426 may display the selected content items 416 and theselected recipients 422 from the interfaces 414, 420. Thus, the inboxowner may review the content to be distributed and the users to whom thecontent will be shared. Optionally, a prompt may be provided forallowing the inbox owner to add explanatory text when the content issent.

When the inbox owner is satisfied, a confirmation indicator 428 may beselected to confirm the transmission of the content. When the indicator428 is selected, the messaging application may transmit the selectedcontent items 416 to the selected recipients 422.

FIG. 4F depicts an exemplary inbox interface 430 for one of therecipients 422, after receiving the content 416 shared in FIGS. 4C-4E. Anew message thread or inbox item 432 may be created in the first sectionof the modular inbox (e.g., the section containing message or threadcontent). The inbox item 432 includes an identification 434 of thesender of the content, along with any explanatory text 436 added duringthe sending process. The shared content item 416 may be displayed in themessage, and interacting with the shared content item 416 may cause theinbox interface 430 to display a larger version of the content item 416(e.g., replacing a thumbnail of the content item 416 with a largerversion), or to navigate to a location of the content item (e.g., takingthe recipient to the recipient's social networking page, in the case ofsocial networking content, or to a web site containing the content).

FIG. 4G is a flowchart depicting an exemplary process 438 for sharingcontent from a module.

At block 440, the messaging application may display a sharing module.The sharing module may be displayed in the second portion of the modularinbox, dedicated to non-message or non-message-thread display. In someembodiments, the module may be configured to share content from a socialnetworking service with users of the messaging service. In otherembodiments, the module may be configured to share local content fromthe local device with users of the messaging service. The module may bedistinct from a portion of the inbox interface that provides message ormessage thread display functionality;

At block 442, the messaging application may identify recommended contentitems for display. The sharing module may be a module for sharing aparticular type of content, such as articles, videos, or pictures, andthe messaging application may identify content of the type associatedwith the sharing module. The sharing module may define where contentitems for the sharing module may be found (e.g., a photo album or rollon the local device for a photos module, a social networking service fora videos module, etc.). The messaging application may retrieve a numberof the content items (e.g., a number defined by the sharing module) fromthe identified location, and may select a recommended subset of theretrieved items for display.

The recommended subset may be determined based on one or more metrics,which may be defined by the sharing module. For example, in the case ofa sharing module for sharing photos, the recommended items may be themost recently captured photographs on the local device. In the case of asharing module for sharing content from a social network, the metricsmay be based on consumption information for the content items. Forinstance, the most consumed or interacted-with content items on thesocial network may be selected as recommended content items. Therecommendation may also be based on a determination of which contentitems the inbox owner is most likely to wish to share (e.g., whichcontent the inbox owner has interacted with recently, or is likely toenjoy based on the inbox owner's interaction history through a socialnetwork).

At block 444, the content items identified in block 442 may be ranked.The content items may be ranked, for example, based on the recency ofthe content item, a predicted likelihood that the inbox owner wouldenjoy the content item, an amount time spent watching the content by theinbox owner or users associated with the inbox owner, etc. One or moreranking metrics may be defined by the sharing module. After the contentitems have been ranked, the sharing module may display the content itemsin ranked order.

At block 446, the sharing module may receive a selection of one or morecontent items to be shared. For example, the messaging application mayregister a touch at a location on a touch-sensitive displaycorresponding to the content item. The messaging application mayregister a selection in other ways, such as through a pointing device,voice commands, etc. The messaging application may update the display toshow an indication (e.g., a check box) on the selected content item.

At block 448, a recommended list of recipients may be identified anddisplayed. The recommended list of recipients may be a subset of theinbox owner's contacts through the messaging service or socialnetworking service.

The recommended list of recipients may be selected based at least inpart on an identity of the content item. For example, a socialnetworking service associated with the networking service may beconsulted to determine which users are most likely to enjoy the contentitem (e.g., based on the users' consumption history through the socialnetwork and/or based on the users' likes and dislikes as indicatedthrough the social graph). In some embodiments, the content item may beassociated with one or more users, who may be identified as recommendedrecipients. For example, a photograph may include the inbox owner andmay also include another member of the messaging service or a socialnetworking service. The other users in the photograph may be selected asrecommended recipients.

Alternatively or in addition, the messaging application may present anoption for selecting a set of recipients not in the list of recommendedrecipients. For example, a menu item may be presented allowing the inboxowner to access their contacts list, and recipients may be selected fromthe contacts list.

At block 450, the sharing module may register a selection of one or morerecipients presented in block 448. For example, the messagingapplication may register a touch at a location on a touch-sensitivedisplay corresponding to the recipient. The messaging application mayregister a selection in other ways, such as through a pointing device,voice commands, etc. The messaging application may update the display toshow an indication (e.g., a check box) on the selected recipient.

At block 452, the messaging application may present a prompt asking thesender to confirm transmission of the selected content item(s) to theselected recipient(s). The messaging application may optionally allowthe sender to add a message to the content item for transmission to therecipients. Upon receiving confirmation of the sender's intent, at block454 the messaging application may share the identified content with theidentified recipients. For example, the messaging application maygenerate a message and/or message thread including the content item andthe sender's message (if any). The messaging application may transmitthe message to the recipients identified at block 450 using themessaging service.

Promotional Material Delivery

Another type of module and/or content item that may be employed in themodular inbox is a promotional material module or content item. FIGS.5A-5D depict various examples of promotional material delivery.

FIG. 5A depicts an example of a promotional material module 502. Thepromotional material module 502 may be a module dedicated to providingpromotional material, such as sponsored items. Promotional content items504 such as advertisements, offers, discounts, etc. may be displayed inthe promotional material module. The promotional content items 504 maybe selected dynamically, such as by determining a location of the clientdevice and selecting promotional content items 504 associated withstores or shops located in close proximity to the client device.

The exemplary promotional material module 502 of FIG. 5A includes twodifferent types of promotional material. A first promotional contentitem 504-1 is a sponsored advertisement prompting a user to purchase agood or service. A second promotional content item 504-2 is a discountoffer that provides the user with an opportunity to receive goods orservices for free or at a discount. Thus, the first content item 504-1is a sponsored advertisement while the second promotional content item504-2 is a discount offer that provides a benefit to a user. Themessaging application may treat these different types of promotionalcontent differently, such as by surfacing the promotional content items504 in different ways depending on whether the content item is anadvertisement or a discount offer.

For example, advertisement content may be surfaced only when a user isin close proximity to the goods or services being advertised, whereas adiscount offer may be displayed at any time. A user may interact withthe promotional content item 504 associated with the discount offer toclaim the discount offer and generate a message related to the discountoffer. At a later time, the user can interact with the message in orderto activate the discount at a retail location.

In another embodiment, advertisements may be relegated to a dedicatedpromotions module 502, whereas discount offers may be interspersed amongthe content of other modules. For example, FIG. 5B depicts an example ofpromotional material integrated into non-promotional material module506.

In this example, the module 506 is a sharing module for sharing articlesfrom a social networking service. The content items of the sharingmodule include various sharable content items 508 in the form ofarticles. A promotional content item 504-2 in the form of a discountoffer is provided among the sharable content items 508. The intra-modulerank of the promotional content item 504-2 (defining where in the modulethe item 504-2 will appear) may depend on a level of sponsorship by thepromoter of the promotional content item 504-2.

In some embodiments, advertisements may also be interspersed innon-promotional materials module. For example, depending on an amount ofsponsorship by the promoter, the promotional content items may bedisplayed higher in the intra-module ranked order, or may be displayedin a non-promotional content module. In another embodiment, the modulein which sponsored content is provided may be elevated in aninter-module ranked order depending on the level of sponsorship.

In some embodiments, a user may be presented with an option to share adiscount offer with their friends, e.g. to encourage the user and theirfriends to gather together at a given location in order to claim theoffer.

As noted above, in some embodiments a user may interact with thepromotional content item 504 associated with the discount offer to claimthe discount offer and generate a message related to the discount offer.FIG. 5C depicts an example of a message 510 generated in response tointeracting with promotional material.

The message 510 may appear as any other message among the user's messagethreads, and may be treated as any other message content for purposes ofthe modular inbox. The message 510 includes message text 512 generatedby a promoter of the promotional content item 504 which describes theoffer being sent. Optionally, the message 510 may also include ascannable code 514, such as a bar code or QR code, which a user maypresent at a retail location in order to claim the offer or discount. Inthe depicted example, scanning the code 514 at a retail location resultsin the user being able to claim a free coffee.

FIG. 5D is a flowchart depicting an exemplary process 516 for providingpromotional content in a module.

At block 518, the messaging application may display a first set ofmessages in a first portion of an inbox interface for a messagingservice. The first portion of the inbox interface may be dedicated to,or may primarily provide, message or thread display functionality. Thefirst portion of the inbox may end at a messaging cliff, as described inmore detail below.

At block 520, the messaging application may receive an instruction tonavigate past the first portion of the inbox interface. For example, themessaging application may register a gesture on a touch screencorresponding to a scrolling gesture, where scrolling the interface inaccordance with the gesture would cause the interface to scroll beyondthe final message or message thread in the first set of messages.Scrolling or navigation may be achieved in other ways as well, such asby interacting with a pointing device (e.g., a computer mouse), voicecommands, etc.

At block 522, the messaging application may select promotional materialfor display. For example, the messaging service may maintain a databaseor other storage of promotional material, and the messaging applicationmay access the database in order to retrieve a number of candidatepromotional materials. To determine which of the candidate promotionalmaterials to display, the messaging application and/or a server of themessaging service may apply one or more metrics, such as: a history ofinteraction between the user and the promoter on the messaging service,a social networking service, or elsewhere; a determined likelihood thatthe user will find an offer from the promoter desirable; or a proximityof the user to a retail location associated with a promotion, amongother possibilities.

In an embodiment employing a proximity metric, block 522 may involvedetecting a location of a mobile client of a user of the messagingservice, and selecting the promotional material based on a proximity ofthe mobile client to a location associated with a source of thepromotional material, such as when the location is determined to bewithin a predetermined distance from the source.

According to some embodiments, block 522 may involve determining if thecandidate promotional material is an advertisement or a discount offer;and selecting a presentation technique for the promotional materialdepending on whether the promotional material is the advertisement orthe discount offer, as described above.

At block 524, the messaging application may display a module in a secondportion of the inbox interface. The module may include some or all ofthe promotional material selected at block 522. The module may bedistinct from the first portion of the inbox interface that provides themessage or message thread display functionality.

In some embodiments, the module may be configured to exclusively sharepromotional material with a user of the messaging service. In otherembodiments, the module may be dedicated to other messaging servicefunctionality, where the functionality is distinct from functionalityfor displaying promotional material. In other words, the promotionalmaterial may be integrated into other, non-promotional modules, with thepromotional material being presented alongside other content of themodule. For example, in the “People/States” module, the inbox interfacemay present a number of friends (e.g., the user's mother, the user'sfriend, etc.) alongside a promoted content item (e.g., a phone company'scustomer service representative, which could be a bot).

The module containing the promotional content may be one among severalmodules that are presented in a ranked order. Depending on a level ofsponsorship of the module containing the promotional content, the rankedorder may be altered. For example, if the sponsors who providedpromotional content in the module provide a sufficiently high level ofsponsorship (above a threshold amount), the module may be elevatedhigher than other modules in the modular inbox.

At block 526, the messaging application may receive a selection ofpromotional material. Depending on the actions defined by the promoterwho provided the promotional material, a number of different actions maybe taken. For example, interacting with the promotional material maytake the user to a web page or social networking site associated withthe promoter.

In some embodiments, interacting with the promotional material may causea message to be generated (block 528). Based on instructions providedwith or associated with the promotional content item selected, messagecontent (potentially including a scannable code) may be automaticallygenerated and transmitted to the inbox owner through the messagingservice. The inbox owner may be provided with an option to share thepromotional content and/or the generated message with other users.

The Cliff

The above-described modules may be displayed after a first subset of theinbox owner's messages in the modular inbox. The cut-off location afterwhich the inbox transitions to modules, rather than messages or messagethreads, is referred to herein as the cliff. FIG. 6 is a flowchartdepicting an exemplary process 600 for determining a transition point(cliff) between a first group of messages and a set of one or moremodules.

At block 602, the messaging application may receive an instruction todisplay an inbox interface for a messaging service. Block 602 may occur,for example, in response to starting up the messaging application or inresponse to receiving an instruction to access a home screen or inboxscreen in the messaging application.

At block 604, the messaging application may determine a number ofmessages to be displayed in a first portion of the inbox interfacecontaining a subset of the messages. The subset may be a number ofmessages that is smaller than the totality of all of the messagesavailable in the user's inbox. In some embodiments, the number may fallbetween a lower threshold for the number of messages threads and anupper threshold for the number of messages.

The lower threshold may be a predetermined minimum number ofmessages/threads. For example, it may be undesirable to display too fewmessages before non-message content is displayed. Thus, thepredetermined minimum may be set to a value (e.g., 2-6 message threads)so that at least a certain number of message threads are displayed priorto non-message content. In some embodiments, the minimum number ofmessages/threads may be dynamically determined using criteria similar tothat discussed below.

The upper threshold may be predetermined, or may be dynamicallydetermined. The upper threshold (and the criteria used to determine theupper threshold) may vary from user to user.

For example, at block 606, the messaging application may dynamicallyselect an upper threshold based on one or more criteria. The criteriamay include, for example, whether the user has participated in at leasta predetermined number of conversations over a predetermined period oftime. For example, if the user is not particularly active, the maximumnumber may be set relatively low (as the user likely only needs to see afew of the most recent conversations). On the other hand, if the user ishighly active, the user may have a number of message threads in whichthey are currently participating, and is likely to wish to see thesethreads at the forefront in the messaging application.

Another criterion may be the number of message threads in which there isa currently active conversation (e.g., a conversation in which the mostrecent message has been received in less than a predetermined thresholdamount of time), and/or the number of message threads having unreadmessages. In some embodiments, the upper threshold may be set such thatthe first portion of the inbox interface shows all of the threads thatinclude an active conversation and any threads that have unreadmessages. The last message to meet either of these criteria may beselected to define the upper threshold.

Another example of a criteria may be historical interactions with themessaging application. For example, if a user utilizes the messagingapplication multiple times per day may wish to see more conversationsthan a user who utilizes the messaging application on a limited basis.

Another example of a criteria is the current time of day. If the currenttime is during the night hours, the user is likely asleep and notmessaging particularly actively. Thus, the system may select arelatively small upper threshold. On the other hand, during the day thethreshold may be increased since the user is likely to be relativelymore active.

Yet another example of a criteria is the amount of time since the lastactive conversation. For example, the messaging application maydetermine the last thread in which a user had an active conversation inthe previous n number of hours (e.g., n=6, 8, 24, etc.). The upperthreshold may be set to encompass the number of active message threadswithin the time window.

The criteria may be combined with each other. For example, the messagingapplication may use the historical interaction information for themessaging application to alter the time window for the amount of timesince the last active conversation. If the user is highly active withthe messaging application, the time window may be set relatively short(e.g., 6 hours or even less), which would likely still result in a largenumber of conversations for an active user. On the other hand, aninactive user might have their time window set relatively long (e.g.,one week), because the longer list of conversations may remind the userto follow up with people from several days ago, thus prompting the userto higher levels of activity. In another example, if the current time ofday is during the user's work hours, the time window may be increased ordecreased depending on whether the user actively uses the messagingservice for work or not. A user actively using the messaging service forwork may wish to see a relatively small number of the most recentmessages, whereas a user that does not use the messaging service maywish to see a larger number of messages encompassing those which theuser missed while at work.

In another embodiment, the number of unread messages and/or activeconversations may be combined with the above-described time window. Forexample, the messaging application may determine the number of unreadmessages/active conversations within the previous n hours. The upperthreshold may be set to encompass these messages and conversations.

If there are no unread messages or active conversations within the timeperiod, then the lower threshold determined at step 604 may be utilized.

At block 608, the messaging application may display the first set ofmessages (i.e., the number of most-recent messages and/or threads thatdo not exceed the lower threshold or the upper threshold, whichever ishigher) in a first portion of the inbox interface. Optionally, themessages of the first set of messages may be displayed, butpreviously-read messages and/or messages without an active conversationmay be filtered out and moved to the second subset of messages.

At block 610, the messaging application may display non-message contentin a second portion of the inbox interface. The second portion mayinclude a number of modules related to functionality of the messagingservice that is not directly related to message or thread displayfunctionality, such as the modules described in connection with FIGS.2A-5D.

At block 612, the messaging application may display the second subset ofmessages. The second subset of messages may be displayed as a result ofan instruction to navigate past the modules displayed in block 610.Following these modules, an additional message inbox may be displayedincluding the previously undisplayed messages/threads. In anotherembodiment, the messages of the second subset may be collapsed into amenu in the first portion of the inbox, as previously described.

Module Ranking

When two or more modules are displayed, an inter-module order may beestablished to define the display order for the modules (e.g., shouldthe Top Contacts Module be displayed before the Photos Module?). If, forexample, the user's mother recently came online, then this informationmay be particularly pertinent and the People/States Module may be a goodcandidate for an early spot among the modules. On the other hand, if aparticular article is being widely shared on the user's socialnetworking service, then a sharing module for sharing articles may beelevated to a top spot.

It is noted that the first portion of the display, including the firstsubset of the messages/message threads, may be treated as a module andmay be ranked among the other modules for display. In some embodiments,the messages/threads module may be locked to the top of the inboxinterface, although in other embodiments it may be allowed to floatamong the other modules depending on its rank. In some embodiments, themessages/threads module may be locked to the top slot unless anothermodule is determined to be extremely relevant (e.g., the probability ofinteraction described in connection with FIGS. 7A and 7B is above apredetermined relatively high threshold), in which case the extremelyrelevant module may be elevated above the messages/threads module.

The inter-module order may be determined based on a dynamicallycalculated inter-module ranking. FIGS. 7A-7B describe how theinter-module ranking is determined, while FIG. 7C describes how contentwithin a module may be ranked. FIG. 7A is a block diagram providing anoverview of a module ranking framework.

Generally speaking, the module ranking framework proceeds in two stages.First, the framework determines how likely a person is to interact withthe module in question. Second, the framework determines a value ofproviding the module to the messaging service. The probability iscombined with the value to determine the module's rank score. The scoresof different modules are compared to each other in order to determinethe modules' ordering. In some embodiments, only modules above apredetermined threshold rank score are presented to a user in the secondportion of the inbox interface.

The framework may evaluate a number of aggregated features 702 and anumber of per-user features 704. The aggregated features 702 may use auser base (e.g., the messaging service's or a social networkingservice's user base) as a proxy for the currently-evaluated user, inorder to evaluate the module's general popularity. The aggregatedfeatures 702 may include data regarding module usage as aggregated overthe user base. For example, the aggregated features 702 may include thenumber of impressions of a given module in a predetermined period oftime (e.g., 30 days) among the user base, the number of times the userbase has interacted with the module in a predetermined period of time(e.g., 30 days), etc.

The per-user features 704 may include similar information, but may bespecific to the user under evaluation (or may otherwise be generated ona per-user basis). For example, the per-user features 704 may include anumber of impressions of a module for a given user-module pair, a numberof interactions with a module for a given user-module pair, etc.

The aggregated features 702 and the per-user features 704 may beretrieved by a feature fetcher 706 for evaluation. The feature fetcher706 may be, for example, a component of a server that retrieves thefeatures from the messaging service and any applicable module providers.The feature fetcher 706 may aggregate the features and provide thefeatures to a scorer 708.

The scorer 708 accepts the features as input and determines aprobability of interaction 712 for the modules described by thefeatures. The probability of interaction 712 may represent a likelihoodthat a given user (or a user in general) will use the module.

The scorer 708 may be supplemented by one or more offline trained models710 that may improve the scorer's 708 predictions in certain contexts.For example, the offline trained models 710 may account for variablessuch as a user's age group, a user's gender, the user's recent posts toa social networking service, etc.

The scorer may determine the probability of interaction 712 according toa formula, such as the one described below in Equation 1:

$\begin{matrix}{{{Probability}\mspace{14mu} {of}\mspace{14mu} {Interaction}} = {{\lambda*\frac{{\# \mspace{14mu} {unit}\mspace{14mu} {clicks}\mspace{14mu} {by}\mspace{14mu} {user}} + 1}{{\# \mspace{14mu} {unit}\mspace{14mu} {impressoins}\mspace{14mu} {by}\mspace{14mu} {user}} + 2}} + {\left( {1 - \lambda} \right)*\frac{{\# \mspace{14mu} {unit}\mspace{14mu} {clicks}} + 1}{{\# \mspace{14mu} {unit}\mspace{14mu} {impressions}} + 2}}}} & {{Equation}\mspace{14mu} 1}\end{matrix}$

Where λ is a personalization multiplier which balances the user'sbehavior and the user base's aggregated behavior. One of ordinary skillin the art will recognize that Equation 1 is exemplary only, and thatother suitable formulae may be used to estimate the probability that auser will interact with a module.

The determined probability of interaction 712 may be provided to a valuemodel estimator 714. The value model estimator 714 may determine a valueof the module to the messaging service or an associated socialnetworking service. For example, it may be more valuable to themessaging service for the current user to start a new thread withanother user (thus encouraging both users to become more active) thanfor the user to share an article with an already-active user, or for theuser to view an advertisement. Thus, the messaging application mayelevate the People/States Module above a Sharable Articles Module or aPromotional Materials Module.

To this end, the value model estimator 714 may consult a value modeldefinition 716 that provides values for each of the modules accessiblethrough the messaging service. The values provided by the value modeldefinition 716 may be combined with the probability of interaction 712to determine a final score for ranking 718 for each module. The scoresfor the modules may be compared to each other to determine relativeranks for the modules.

The above-described framework may be employed in an exemplary process720 for determining an inter-module rank. FIG. 7B depicts an example ofsuch a process 720.

At block 722, the messaging service may identify a first module andsecond module available for display by a client's messaging application.The first module and the second module may provide access tofunctionality of the messaging service that is distinct from message orthread display functionality.

At block 724, the messaging service may determine probabilities ofinteraction for the first module and the second module, such as theprobability of interaction 712 discussed in connection with FIG. 7A. Theprobabilities of interaction may represent a likelihood that the inboxowner will use the first module and the second module, respectively.

As an alternative or in addition to the probability of interaction 712as calculated n FIG. 7A, each module may provide its own estimation ofthe likelihood that the inbox owner will use the module. For example,each module may provide a number that reflects the quality of contentcurrently available through the module (e.g., the quality of the contenttoday as compared to the average day).

The probability of interaction may be augmented or may take into accountother criteria, such as recency. For example, if a user takes a photowith their mobile device and then immediately accesses the messagingapplication, there may be an elevated likelihood that the user wishes toshare the recently captured photograph with their messaging contacts. Inanother embodiment, the messaging application (or a related socialnetworking service) may identify one or more other users in the photo,and may determine if the current user and the other users are highlyconnected or are highly likely to message each other. Such a coefficientmay be used to elevate the priority of a module for sharing the photo,if other highly connected users are available through the messagingservice.

At block 726, the messaging service may determine a value of the firstmodule and the second module to the messaging service or a relatedsocial networking service. Block 726 may be carried out by the valuemodel estimator 714 of FIG. 7A.

At block 728, the message service may determine a ranked order for thefirst module and the second module by combining the probabilitydetermined at block 724 with the value determined at block 726. Forexample, the probability of interaction may be multiplied by (orotherwise combined with) the value in order to determine a rankingscore, and the modules may be ranked in the order of their respectiveranking scores.

At block 730, the messaging service may determine intra-module rankingsfor the content of the first and second modules. This may involvearranging the content within the first module and/or the second modulein an intra-module ranked order, as described in more detail inconnection with FIG. 7C. Depending on whether certain content in amodule is particularly relevant, then at block 732 the inter-moduleranked order as determined at block 728 may be altered (e.g., to elevatea module having particularly relevant content).

At block 734, the first module and the second module may be displayed inthe ranked order after a first subset of messages in the inboxinterface.

FIG. 7C is a flowchart depicting an exemplary process performed by block730, for determining an intra-module rank, in more detail. In general,the messaging service may be agnostic to the intra-module ranking, thusallowing each module to define its own intra-module ranking for content.

At block 738, the messaging service may identify a first content itemand a second content item for a given module. The module may provide ordefine a location from which content items for the module may beretrieved.

At block 740, the messaging service may access ranking rules as providedby the module. Depending on the content, for example, the module maydesignate different criteria to be applied to rank the content.Exemplary criteria for ranking content within a module include a recencyof the content, an importance of the content to a user, or an affinityfor the content by the user, etc.

At block 742, the messaging service may determine a recency of thecontent, or any other information required by the criteria. Theinformation about the criteria may be retrieved, for example, from asocial networking service, the messaging service, a client device, or aremote location associated with the module.

At block 744, the system may determine a user affinity for the contentitems. The user affinity may represent a user affinity score 746 thatindicates a likelihood that the inbox owner will enjoy the content.Alternatively or in addition, the user affinity may represent anassociate affinity score 748 that indicates a likelihood that associatesof the inbox owner (e.g., the inbox owner's friends through a socialnetworking service or contacts through the messaging service) will enjoythe content.

At block 750, the messaging service may rank the first and secondcontent items based on the affinity score(s) determined at block 744.Optionally, if one or more of the affinity scores exceeds apredetermined threshold (e.g., indicating that a content item isparticularly relevant), then at block 752 the messaging service may flagthe module containing the content for adjustment in the inter-modulerankings.

At block 756, the messaging service may display the first and secondcontent items within the module in the ranked order.

Messaging System Overview

These examples may be implemented by a messaging system that is providedeither locally, at a client device, or remotely (e.g., at a remoteserver). FIGS. 8A-8C depict various examples of messaging systems, andare discussed in more detail below.

FIG. 8A depicts an exemplary centralized messaging system 800, in whichfunctionality for organizing messages asynchronously and/or usingthreads is integrated into a messaging server. The centralized system800 may implement some or all of the structure and/or operations of amessaging service in a single computing entity, such as entirely withina single centralized server device 826.

The messaging system 800 may include a computer-implemented systemhaving software applications that include one or more components.Although the messaging system 800 shown in FIG. 8A has a limited numberof elements in a certain topology, the messaging system 800 may includemore or fewer elements in alternate topologies.

A messaging service 800 may be generally arranged to receive, store, anddeliver messages. The messaging service 800 may store messages whilemessaging clients 820, such as may execute on client devices 810, areoffline and deliver the messages once the messaging clients areavailable.

A client device 810 may transmit messages addressed to a recipient user,user account, or other identifier resolving to a receiving client device810. In exemplary embodiments, each of the client devices 810 and theirrespective messaging clients 820 are associated with a particular useror users of the messaging service 800. In some embodiments, the clientdevices 810 may be cellular devices such as smartphones and may beidentified to the messaging service 800 based on a phone numberassociated with each of the client devices 810. In some embodiments,each messaging client may be associated with a user account registeredwith the messaging service 800. In general, each messaging client may beaddressed through various techniques for the reception of messages.While in some embodiments the client devices 810 may be cellulardevices, in other embodiments one or more of the client devices 810 maybe personal computers, tablet devices, any other form of computingdevice.

The client 810 may include one or more input devices 812 and one or moreoutput devices 818. The input devices 812 may include, for example,microphones, keyboards, cameras, electronic pens, touch screens, andother devices for receiving inputs including message data, requests,commands, user interface interactions, selections, and other types ofinput. The output devices 818 may include a speaker, a display devicesuch as a monitor or touch screen, and other devices for presenting aninterface to the messaging system 800.

The client 810 may include a memory 819, which may be a non-transitorycomputer readable storage medium, such as one or a combination of a harddrive, solid state drive, flash storage, read only memory, or randomaccess memory. The memory 819 may a representation of an input 814and/or a representation of an output 816, as well as one or moreapplications. For example, the memory 819 may store a messaging client820 and/or a social networking client that allows a user to interactwith a social networking service.

The input 814 may be textual, such as in the case where the input device212 is a keyboard. Alternatively, the input 814 may be an audiorecording, such as in the case where the input device 812 is amicrophone. Accordingly, the input 814 may be subjected to automaticspeech recognition (ASR) logic in order to transform the audio recordingto text that is processable by the messaging system 800. The ASR logicmay be located at the client device 810 (so that the audio recording isprocessed locally by the client 810 and corresponding text istransmitted to the messaging server 826), or may be located remotely atthe messaging server 826 (in which case, the audio recording may betransmitted to the messaging server 826 and the messaging server 826 mayprocess the audio into text). Other combinations are also possible—forexample, if the input device 812 is a touch pad or electronic pen, theinput 814 may be in the form of handwriting, which may be subjected tohandwriting or optical character recognition analysis logic in order totransform the input 812 into processable text.

The client 810 may be provided with a network interface 822 forcommunicating with a network 824, such as the Internet. The networkinterface 822 may transmit the input 812 in a format and/or using aprotocol compatible with the network 824 and may receive a correspondingoutput 816 from the network 824.

The network interface 822 may communicate through the network 824 to amessaging server 826. The messaging server 826 may be operative toreceive, store, and forward messages between messaging clients.

The messaging server 826 may include a network interface 822, messagingpreferences 828, and messaging inbox logic 830. The messagingpreferences 828 may include one or more privacy settings for one or moreusers and/or message threads. For example, the messaging preferences 828may include a setting that indicates whether to display messagessynchronously or asynchronously. Furthermore, the messaging preferences828 may include one or more settings, including default settings, forthe logic described herein.

The messaging inbox logic 830 may include the logic for generating andmaintaining a modular inbox as described above. For example, themessaging inbox logic 830 may include module logic 832 that is operableto generate modules for the inbox and manage interactions with themodules. The module logic 832 may include, for example, logic similar tothat described in connection with FIGS. 3, 4G, 5D, and 6. The messaginginbox logic 830 may further include ranking logic 834 that is operableto perform inter-module and intra-module ranking, such as the logicdescribed in connection with FIGS. 7B-7C.

The network interface 822 of the client 810 and/or the messaging server826 may also be used to communicate through the network 824 with asocial networking server 836. The social networking server 836 mayinclude or may interact with a social networking graph 838 that definesconnections in a social network. Furthermore, the messaging server 826may connect to the social networking server 836 for various purposes,such as retrieving connection information, messaging history, eventdetails, etc. from the social network.

A user of the client 810 may be an individual (human user), an entity(e.g., an enterprise, business, or third-party application), or a group(e.g., of individuals or entities) that interacts or communicates withor over the social networking server 836. The social-networking server836 may be a network-addressable computing system hosting an onlinesocial network. The social networking server 836 may generate, store,receive, and send social-networking data, such as, for example,user-profile data, concept-profile data, social-graph information, orother suitable data related to the online social network. The socialnetworking server 836 may be accessed by the other components of thenetwork environment either directly or via the network 824.

The social networking server 836 may include an authorization server (orother suitable component(s)) that allows users to opt in to or opt outof having their actions logged by social-networking server 836 or sharedwith other systems (e.g., third-party systems, such as the messagingserver 826), for example, by setting appropriate privacy settings. Aprivacy setting of a user may determine what information associated withthe user may be logged, how information associated with the user may belogged, when information associated with the user may be logged, who maylog information associated with the user, whom information associatedwith the user may be shared with, and for what purposes informationassociated with the user may be logged or shared. Authorization serversmay be used to enforce one or more privacy settings of the users ofsocial-networking server 836 through blocking, data hashing,anonymization, or other suitable techniques as appropriate.

More specifically, one or more of the content objects of the onlinesocial network may be associated with a privacy setting. The privacysettings (or “access settings”) for an object may be stored in anysuitable manner, such as, for example, in association with the object,in an index on an authorization server, in another suitable manner, orany combination thereof. A privacy setting of an object may specify howthe object (or particular information associated with an object) can beaccessed (e.g., viewed or shared) using the online social network. Wherethe privacy settings for an object allow a particular user to accessthat object, the object may be described as being “visible” with respectto that user. As an example and not by way of limitation, a user of theonline social network may specify privacy settings for a user-profilepage identify a set of users that may access the work experienceinformation on the user-profile page, thus excluding other users fromaccessing the information. In particular embodiments, the privacysettings may specify a “blocked list” of users that should not beallowed to access certain information associated with the object. Inother words, the blocked list may specify one or more users or entitiesfor which an object is not visible. As an example and not by way oflimitation, a user may specify a set of users that may not access photosalbums associated with the user, thus excluding those users fromaccessing the photo albums (while also possibly allowing certain usersnot within the set of users to access the photo albums).

In particular embodiments, privacy settings may be associated withparticular elements of the social networking graph 838. Privacy settingsof a social-graph element, such as a node or an edge, may specify howthe social-graph element, information associated with the social-graphelement, or content objects associated with the social-graph element canbe accessed using the online social network. As an example and not byway of limitation, a particular concept node corresponding to aparticular photo may have a privacy setting specifying that the photomay only be accessed by users tagged in the photo and their friends. Inparticular embodiments, privacy settings may allow users to opt in oropt out of having their actions logged by social networking server 836or shared with other systems. In particular embodiments, the privacysettings associated with an object may specify any suitable granularityof permitted access or denial of access. As an example and not by way oflimitation, access or denial of access may be specified for particularusers (e.g., only me, my roommates, and my boss), users within aparticular degrees-of-separation (e.g., friends, or friends-of-friends),user groups (e.g., the gaming club, my family), user networks (e.g.,employees of particular employers, students or alumni of particularuniversity), all users (“public”), no users (“private”), users ofthird-party systems, particular applications (e.g., third-partyapplications, external websites), other suitable users or entities, orany combination thereof. Although this disclosure describes usingparticular privacy settings in a particular manner, this disclosurecontemplates using any suitable privacy settings in any suitable manner.

In response to a request from a user (or other entity) for a particularobject stored in a data store, the social networking server 836 may senda request to the data store for the object. The request may identify theuser associated with the request. The requested data object may only besent to the user (or a client system 810 of the user) if theauthorization server determines that the user is authorized to accessthe object based on the privacy settings associated with the object. Ifthe requesting user is not authorized to access the object, theauthorization server may prevent the requested object from beingretrieved from the data store, or may prevent the requested object frombe sent to the user. In the search query context, an object may only begenerated as a search result if the querying user is authorized toaccess the object. In other words, the object must have a visibilitythat is visible to the querying user. If the object has a visibilitythat is not visible to the user, the object may be excluded from thesearch results.

In some embodiments, targeting criteria may be used to identify users ofthe social network for various purposes. Targeting criteria used toidentify and target users may include explicit, stated user interests onsocial-networking server 836 or explicit connections of a user to anode, object, entity, brand, or page on social networking server 836. Inaddition, or as an alternative, such targeting criteria may includeimplicit or inferred user interests or connections (which may includeanalyzing a user's history, demographic, social or other activities,friends' social or other activities, subscriptions, or any of thepreceding of other users similar to the user (based, e.g., on sharedinterests, connections, or events)). Particular embodiments may utilizeplatform targeting, which may involve platform and “like” impressiondata; contextual signals (e.g., “Who is viewing now or has viewedrecently the page for COCA-COLA?”); light-weight connections (e.g.,“check-ins”); connection lookalikes; fans; extracted keywords; EMUadvertising; inferential advertising; coefficients, affinities, or othersocial-graph information; friends-of-friends connections; pinning orboosting; deals; polls; household income, social clusters or groups;products detected in images or other media; social- or open-graph edgetypes; geo-prediction; views of profile or pages; status updates orother user posts (analysis of which may involve natural-languageprocessing or keyword extraction); events information; or collaborativefiltering. Identifying and targeting users may also implicate privacysettings (such as user opt-outs), data hashing, or data anonymization,as appropriate.

The centralized embodiment depicted in FIG. 8A may be well-suited todeployment as a new system or as an upgrade to an existing system,because the logic for pivoting to a group conversation (e.g., the logicof the account identifier 832 and/or the logic of the account notifier834) are incorporated into the messaging server 826. In contrast, FIG.8B depicts an exemplary distributed messaging system 880, in whichfunctionality for recognizing productive intent and generating a list ofsuggested recipients is distributed and remotely accessible from themessaging server. Examples of a distributed system 880 include aclient-server architecture, a 3-tier architecture, an N-tierarchitecture, a tightly-coupled or clustered architecture, apeer-to-peer architecture, a master-slave architecture, a shareddatabase architecture, and other types of distributed systems.

Many of the components depicted in FIG. 8B are identical to those inFIG. 8A, and a description of these elements is not repeated here forthe sake of brevity. The primary difference between the centralizedembodiment and the distributed embodiment is the addition of a separatethreading server 882, which hosts the thread creation component 832 andthe thread display component 834. The threading server 882 may bedistinct from the messaging server 826 but may communicate with themessaging server 826, either directly or through the network 824, toprovide the functionality of the account identifier 832 and the accountnotifier 834 to the messaging server 826.

The embodiment depicted in FIG. 8B may be particularly well suited toallow exemplary embodiments to be deployed alongside existing messagingsystems, for example when it is difficult or undesirable to replace anexisting messaging server. Additionally, in some cases the messagingserver 826 may have limited resources (e.g. processing or memoryresources) that limit or preclude the addition of the additional pivotfunctionality. In such situations, the capabilities described herein maystill be provided through the separate pivot server 882.

FIG. 8C illustrates an example of a social networking graph 838. Inexemplary embodiments, a social networking service may store one or moresocial graphs 838 in one or more data stores as a social graph datastructure via the social networking service.

The social graph 838 may include multiple nodes, such as user nodes 854and concept nodes 856. The social graph 838 may furthermore includeedges 858 connecting the nodes. The nodes and edges of social graph 838may be stored as data objects, for example, in a data store (such as asocial-graph database). Such a data store may include one or moresearchable or queryable indexes of nodes or edges of social graph 838.

The social graph 838 may be accessed by a social-networking server 826,client system 810, third-party system, or any other approved system ordevice for suitable applications.

A user node 854 may correspond to a user of the social-networkingsystem. A user may be an individual (human user), an entity (e.g., anenterprise, business, or third-party application), or a group (e.g., ofindividuals or entities) that interacts or communicates with or over thesocial-networking system. In exemplary embodiments, when a userregisters for an account with the social-networking system, thesocial-networking system may create a user node 854 corresponding to theuser, and store the user node 854 in one or more data stores. Users anduser nodes 854 described herein may, where appropriate, refer toregistered users and user nodes 854 associated with registered users. Inaddition or as an alternative, users and user nodes 854 described hereinmay, where appropriate, refer to users that have not registered with thesocial-networking system. In particular embodiments, a user node 854 maybe associated with information provided by a user or informationgathered by various systems, including the social-networking system. Asan example and not by way of limitation, a user may provide their name,profile picture, contact information, birth date, sex, marital status,family status, employment, education background, preferences, interests,or other demographic information. In particular embodiments, a user node854 may be associated with one or more data objects corresponding toinformation associated with a user. In particular embodiments, a usernode 854 may correspond to one or more webpages. A user node 854 may beassociated with a unique user identifier for the user in thesocial-networking system.

In particular embodiments, a concept node 856 may correspond to aconcept. As an example and not by way of limitation, a concept maycorrespond to a place (such as, for example, a movie theater,restaurant, landmark, or city); a website (such as, for example, awebsite associated with the social-network service or a third-partywebsite associated with a web-application server); an entity (such as,for example, a person, business, group, sports team, or celebrity); aresource (such as, for example, an audio file, video file, digitalphoto, text file, structured document, or application) which may belocated within the social-networking system or on an external server,such as a web-application server; real or intellectual property (suchas, for example, a sculpture, painting, movie, game, song, idea,photograph, or written work); a game; an activity; an idea or theory;another suitable concept; or two or more such concepts. A concept node556 may be associated with information of a concept provided by a useror information gathered by various systems, including thesocial-networking system. As an example and not by way of limitation,information of a concept may include a name or a title; one or moreimages (e.g., an image of the cover page of a book); a location (e.g.,an address or a geographical location); a website (which may beassociated with a URL); contact information (e.g., a phone number or anemail address); other suitable concept information; or any suitablecombination of such information. In particular embodiments, a conceptnode 856 may be associated with one or more data objects correspondingto information associated with concept node 856. In particularembodiments, a concept node 856 may correspond to one or more webpages.

In particular embodiments, a node in social graph 838 may represent orbe represented by a webpage (which may be referred to as a “profilepage”). Profile pages may be hosted by or accessible to thesocial-networking system. Profile pages may also be hosted onthird-party websites associated with a third-party server. As an exampleand not by way of limitation, a profile page corresponding to aparticular external webpage may be the particular external webpage andthe profile page may correspond to a particular concept node 856.Profile pages may be viewable by all or a selected subset of otherusers. As an example and not by way of limitation, a user node 854 mayhave a corresponding user-profile page in which the corresponding usermay add content, make declarations, or otherwise express himself orherself. A business page may comprise a user-profile page for a commerceentity. As another example and not by way of limitation, a concept node856 may have a corresponding concept-profile page in which one or moreusers may add content, make declarations, or express themselves,particularly in relation to the concept corresponding to concept node856.

In particular embodiments, a concept node 856 may represent athird-party webpage or resource hosted by a third-party system. Thethird-party webpage or resource may include, among other elements,content, a selectable or other icon, or other inter-actable object(which may be implemented, for example, in JavaScript, AJAX, or PHPcodes) representing an action or activity. As an example and not by wayof limitation, a third-party webpage may include a selectable icon suchas “like,” “check in,” “eat,” “recommend,” or another suitable action oractivity. A user viewing the third-party webpage may perform an actionby selecting one of the icons (e.g., “eat”), causing a client system tosend to the social-networking system a message indicating the user'saction. In response to the message, the social-networking system maycreate an edge (e.g., an “eat” edge) between a user node 854corresponding to the user and a concept node 856 corresponding to thethird-party webpage or resource and store edge 858 in one or more datastores.

In particular embodiments, a pair of nodes in social graph 838 may beconnected to each other by one or more edges 858. An edge 858 connectinga pair of nodes may represent a relationship between the pair of nodes.In particular embodiments, an edge 858 may include or represent one ormore data objects or attributes corresponding to the relationshipbetween a pair of nodes. As an example and not by way of limitation, afirst user may indicate that a second user is a “friend” of the firstuser. In response to this indication, the social-networking system maysend a “friend request” to the second user. If the second user confirmsthe “friend request,” the social-networking system may create an edge858 connecting the first user's user node 854 to the second user's usernode 854 in social graph 838 and store edge 858 as social-graphinformation in one or more data stores. In the example of FIG. 8C,social graph 838 includes an edge 858 indicating a friend relationbetween user nodes 854 of user “Amanda” and user “Dorothy.” Althoughthis disclosure describes or illustrates particular edges 858 withparticular attributes connecting particular user nodes 854, thisdisclosure contemplates any suitable edges 858 with any suitableattributes connecting user nodes 854. As an example and not by way oflimitation, an edge 858 may represent a friendship, family relationship,business or employment relationship, fan relationship, followerrelationship, visitor relationship, subscriber relationship,superior/subordinate relationship, reciprocal relationship,non-reciprocal relationship, another suitable type of relationship, ortwo or more such relationships. Moreover, although this disclosuregenerally describes nodes as being connected, this disclosure alsodescribes users or concepts as being connected. Herein, references tousers or concepts being connected may, where appropriate, refer to thenodes corresponding to those users or concepts being connected in socialgraph 838 by one or more edges 858.

In particular embodiments, an edge 858 between a user node 854 and aconcept node 856 may represent a particular action or activity performedby a user associated with user node 854 toward a concept associated witha concept node 856. As an example and not by way of limitation, asillustrated in FIG. 8C, a user may “like,” “attended,” “played,”“listened,” “cooked,” “worked at,” or “watched” a concept, each of whichmay correspond to an edge type or subtype. A concept-profile pagecorresponding to a concept node 856 may include, for example, aselectable “check in” icon (such as, for example, a clickable “check in”icon) or a selectable “add to favorites” icon. Similarly, after a userclicks these icons, the social-networking system may create a “favorite”edge or a “check in” edge in response to a user's action correspondingto a respective action. As another example and not by way of limitation,a user (user “Carla”) may listen to a particular song (“Across the Sea”)using a particular application (SPOTIFY, which is an online musicapplication). In this case, the social-networking system may create a“listened” edge 858 and a “used” edge (as illustrated in FIG. 8C)between user nodes 854 corresponding to the user and concept nodes 856corresponding to the song and application to indicate that the userlistened to the song and used the application. Moreover, thesocial-networking system may create a “played” edge 858 (as illustratedin FIG. 8C) between concept nodes 856 corresponding to the song and theapplication to indicate that the particular song was played by theparticular application. In this case, “played” edge 858 corresponds toan action performed by an external application (SPOTIFY) on an externalaudio file (the song “Across the Sea”). Although this disclosuredescribes particular edges 858 with particular attributes connectinguser nodes 854 and concept nodes 856, this disclosure contemplates anysuitable edges 858 with any suitable attributes connecting user nodes854 and concept nodes 856. Moreover, although this disclosure describesedges between a user node 854 and a concept node 856 representing asingle relationship, this disclosure contemplates edges between a usernode 854 and a concept node 856 representing one or more relationships.As an example and not by way of limitation, an edge 858 may representboth that a user likes and has used at a particular concept.Alternatively, another edge 858 may represent each type of relationship(or multiples of a single relationship) between a user node 854 and aconcept node 856 (as illustrated in FIG. 8C between user node 854 foruser “Edwin” and concept node 856 for “SPOTIFY”).

In particular embodiments, the social-networking system may create anedge 858 between a user node 854 and a concept node 856 in social graph838. As an example and not by way of limitation, a user viewing aconcept-profile page (such as, for example, by using a web browser or aspecial-purpose application hosted by the user's client system) mayindicate that he or she likes the concept represented by the conceptnode 856 by clicking or selecting a “Like” icon, which may cause theuser's client system to send to the social-networking system a messageindicating the user's liking of the concept associated with theconcept-profile page. In response to the message, the social-networkingsystem may create an edge 858 between user node 854 associated with theuser and concept node 856, as illustrated by “like” edge 858 between theuser and concept node 856. In particular embodiments, thesocial-networking system may store an edge 858 in one or more datastores. In particular embodiments, an edge 858 may be automaticallyformed by the social-networking system in response to a particular useraction. As an example and not by way of limitation, if a first useruploads a picture, watches a movie, or listens to a song, an edge 858may be formed between user node 854 corresponding to the first user andconcept nodes 856 corresponding to those concepts. Although thisdisclosure describes forming particular edges 858 in particular manners,this disclosure contemplates forming any suitable edges 858 in anysuitable manner.

The social graph 838 may further comprise a plurality of product nodes.Product nodes may represent particular products that may be associatedwith a particular business. A business may provide a product catalog toa consumer-to-business service and the consumer-to-business service maytherefore represent each of the products within the product in thesocial graph 838 with each product being in a distinct product node. Aproduct node may comprise information relating to the product, such aspricing information, descriptive information, manufacturer information,availability information, and other relevant information. For example,each of the items on a menu for a restaurant may be represented withinthe social graph 838 with a product node describing each of the items. Aproduct node may be linked by an edge to the business providing theproduct. Where multiple businesses provide a product, each business mayhave a distinct product node associated with its providing of theproduct or may each link to the same product node. A product node may belinked by an edge to each user that has purchased, rated, owns,recommended, or viewed the product, with the edge describing the natureof the relationship (e.g., purchased, rated, owns, recommended, viewed,or other relationship). Each of the product nodes may be associated witha graph id and an associated merchant id by virtue of the linkedmerchant business. Products available from a business may therefore becommunicated to a user by retrieving the available product nodes linkedto the user node for the business within the social graph 838. Theinformation for a product node may be manipulated by thesocial-networking system as a product object that encapsulatesinformation regarding the referenced product.

As such, the social graph 838 may be used to infer shared interests,shared experiences, or other shared or common attributes of two or moreusers of a social-networking system. For instance, two or more userseach having an edge to a common business, product, media item,institution, or other entity represented in the social graph 838 mayindicate a shared relationship with that entity, which may be used tosuggest customization of a use of a social-networking system, includinga messaging system, for one or more users.

The embodiments described above may be performed by a messagingarchitecture, an example of which is next described with reference toFIG. 9.

Messaging Architecture

FIG. 9 illustrates an embodiment of a plurality of servers implementingvarious functions of a messaging service 900. It will be appreciatedthat different distributions of work and functions may be used invarious embodiments of a messaging service 900.

The messaging service 900 may comprise a domain name front end 902. Thedomain name front end 902 may be assigned one or more domain namesassociated with the messaging service 900 in a domain name system (DNS).The domain name front end 902 may receive incoming connections anddistribute the connections to servers providing various messagingservices.

The messaging service 902 may comprise one or more chat servers 904. Thechat servers 904 may comprise front-end servers for receiving andtransmitting user-to-user messaging updates such as chat messages.Incoming connections may be assigned to the chat servers 904 by thedomain name front end 902 based on workload balancing.

The messaging service 900 may comprise backend servers 908. The backendservers 908 may perform specialized tasks in the support of the chatoperations of the front-end chat servers 904. A plurality of differenttypes of backend servers 908 may be used. It will be appreciated thatthe assignment of types of tasks to different backend serves 908 mayvary in different embodiments. In some embodiments some of the back-endservices provided by dedicated servers may be combined onto a singleserver or a set of servers each performing multiple tasks dividedbetween different servers in the embodiment described herein. Similarly,in some embodiments tasks of some of dedicated back-end serversdescribed herein may be divided between different servers of differentserver groups.

The messaging service 900 may comprise one or more offline storageservers 910. The one or more offline storage servers 910 may storemessaging content for currently-offline messaging clients in hold forwhen the messaging clients reconnect.

The messaging service 900 may comprise one or more sessions servers 912.The one or more session servers 912 may maintain session state ofconnected messaging clients.

The messaging service 900 may comprise one or more presence servers 914.The one or more presence servers 914 may maintain presence informationfor the messaging service 900. Presence information may correspond touser-specific information indicating whether or not a given user has anonline messaging client and is available for chatting, has an onlinemessaging client but is currently away from it, does not have an onlinemessaging client, and any other presence state.

The messaging service 900 may comprise one or more push storage servers916. The one or more push storage servers 916 may cache push requestsand transmit the push requests to messaging clients. Push requests maybe used to wake messaging clients, to notify messaging clients that amessaging update is available, and to otherwise performserver-side-driven interactions with messaging clients.

The messaging service 900 may comprise one or more group servers 918.The one or more group servers 918 may maintain lists of groups, addusers to groups, remove users from groups, and perform the reception,caching, and forwarding of group chat messages.

The messaging service 900 may comprise one or more block list servers920. The one or more block list servers 920 may maintain user-specificblock lists, the user-specific incoming-block lists indicating for eachuser the one or more other users that are forbidden from transmittingmessages to that user. Alternatively or additionally, the one or moreblock list servers 920 may maintain user-specific outgoing-block listsindicating for each user the one or more other users that that user isforbidden from transmitting messages to. It will be appreciated thatincoming-block lists and outgoing-block lists may be stored incombination in, for example, a database, with the incoming-block listsand outgoing-block lists representing different views of a samerepository of block information.

The messaging service 900 may comprise one or more last seen informationservers 922. The one or more last seen information servers 922 mayreceive, store, and maintain information indicating the last seenlocation, status, messaging client, and other elements of a user's lastseen connection to the messaging service 900.

The messaging service 900 may comprise one or more key servers 924. Theone or more key servers may host public keys for public/private keyencrypted communication.

The messaging service 900 may comprise one or more profile photo servers926. The one or more profile photo servers 926 may store and makeavailable for retrieval profile photos for the plurality of users of themessaging service 900.

The messaging service 900 may comprise one or more spam logging servers928. The one or more spam logging servers 928 may log known andsuspected spam (e.g., unwanted messages, particularly those of apromotional nature). The one or more spam logging servers 928 may beoperative to analyze messages to determine whether they are spam and toperform punitive measures, in some embodiments, against suspectedspammers (users that send spam messages).

The messaging service 900 may comprise one or more statistics servers930. The one or more statistics servers may compile and store statisticsinformation related to the operation of the messaging service 900 andthe behavior of the users of the messaging service 900.

The messaging service 900 may comprise one or more web servers 932. Theone or more web servers 932 may engage in hypertext transport protocol(HTTP) and hypertext transport protocol secure (HTTPS) connections withweb browsers.

The messaging service 900 may comprise one or more chat activitymonitoring servers 934. The one or more chat activity monitoring servers934 may monitor the chats of users to determine unauthorized ordiscouraged behavior by the users of the messaging service 900. The oneor more chat activity monitoring servers 934 may work in cooperationwith the spam logging servers 928 and block list servers 920, with theone or more chat activity monitoring servers 934 identifying spam orother discouraged behavior and providing spam information to the spamlogging servers 928 and blocking information, where appropriate to theblock list servers 920.

The messaging service 900 may comprise one or more sync servers 936. Theone or more sync servers 936 may sync the messaging system 500 withcontact information from a messaging client, such as an address book ona mobile phone, to determine contacts for a user in the messagingservice 900.

The messaging service 900 may comprise one or more multimedia servers938. The one or more multimedia servers may store multimedia (e.g.,images, video, audio) in transit between messaging clients, multimediacached for offline endpoints, and may perform transcoding of multimedia.

The messaging service 900 may comprise one or more payment servers 940.The one or more payment servers 940 may process payments from users. Theone or more payment servers 940 may connect to external third-partyservers for the performance of payments.

The messaging service 900 may comprise one or more registration servers942. The one or more registration servers 942 may register new users ofthe messaging service 900.

The messaging service 900 may comprise one or more voice relay servers944. The one or more voice relay servers 944 may relayvoice-over-internet-protocol (VoIP) voice communication betweenmessaging clients for the performance of VoIP calls.

The above-described methods may be embodied as instructions on acomputer readable medium or as part of a computing architecture. FIG. 10illustrates an embodiment of an exemplary computing architecture 1000suitable for implementing various embodiments as previously described.In one embodiment, the computing architecture 1000 may comprise or beimplemented as part of an electronic device, such as a computer 1001.The embodiments are not limited in this context.

As used in this application, the terms “system” and “component” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are provided by the exemplary computingarchitecture 1000. For example, a component can be, but is not limitedto being, a process running on a processor, a processor, a hard diskdrive, multiple storage drives (of optical and/or magnetic storagemedium), an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration, both an application runningon a server and the server can be a component. One or more componentscan reside within a process and/or thread of execution, and a componentcan be localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 1000 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 1000.

As shown in FIG. 10, the computing architecture 1000 comprises aprocessing unit 1002, a system memory 1004 and a system bus 1006. Theprocessing unit 1002 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 1002.

The system bus 1006 provides an interface for system componentsincluding, but not limited to, the system memory 1004 to the processingunit 1002. The system bus 1006 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 1006 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 1000 may comprise or implement variousarticles of manufacture. An article of manufacture may comprise acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Embodiments may also beat least partly implemented as instructions contained in or on anon-transitory computer-readable medium, which may be read and executedby one or more processors to enable performance of the operationsdescribed herein.

The system memory 1004 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedembodiment shown in FIG. 10, the system memory 1004 can includenon-volatile memory 1008 and/or volatile memory 1010. A basicinput/output system (BIOS) can be stored in the non-volatile memory1008.

The computing architecture 1000 may include various types ofcomputer-readable storage media in the form of one or more lower speedmemory units, including an internal (or external) hard disk drive (HDD)1012, a magnetic floppy disk drive (FDD) 1014 to read from or write to aremovable magnetic disk 1016, and an optical disk drive 1018 to readfrom or write to a removable optical disk 1020 (e.g., a CD-ROM or DVD).The HDD 1012, FDD 1014 and optical disk drive 1020 can be connected tothe system bus 1006 by an HDD interface 1022, an FDD interface 1024 andan optical drive interface 1026, respectively. The HDD interface 1022for external drive implementations can include at least one or both ofUniversal Serial Bus (USB) and IEEE 694 interface technologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 1008, 1012, including anoperating system 1028, one or more application programs 1030, otherprogram modules 1032, and program data 1034. In one embodiment, the oneor more application programs 1030, other program modules 1032, andprogram data 1034 can include, for example, the various applicationsand/or components of the messaging system 500.

A user can enter commands and information into the computer 1001 throughone or more wire/wireless input devices, for example, a keyboard 1036and a pointing device, such as a mouse 1038. Other input devices mayinclude microphones, infra-red (IR) remote controls, radio-frequency(RF) remote controls, game pads, stylus pens, card readers, dongles,finger print readers, gloves, graphics tablets, joysticks, keyboards,retina readers, touch screens (e.g., capacitive, resistive, etc.),trackballs, trackpads, sensors, styluses, and the like. These and otherinput devices are often connected to the processing unit 1002 through aninput device interface 1040 that is coupled to the system bus 1006, butcan be connected by other interfaces such as a parallel port, IEEE 694serial port, a game port, a USB port, an IR interface, and so forth.

A monitor 1042 or other type of display device is also connected to thesystem bus 1006 via an interface, such as a video adaptor 1044. Themonitor 1042 may be internal or external to the computer 1001. Inaddition to the monitor 1042, a computer typically includes otherperipheral output devices, such as speakers, printers, and so forth.

The computer 1001 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 1044. The remote computer1044 can be a workstation, a server computer, a router, a personalcomputer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1001, although, for purposes of brevity, only a memory/storage device1046 is illustrated. The logical connections depicted includewire/wireless connectivity to a local area network (LAN) 1048 and/orlarger networks, for example, a wide area network (WAN) 1050. Such LANand WAN networking environments are commonplace in offices andcompanies, and facilitate enterprise-wide computer networks, such asintranets, all of which may connect to a global communications network,for example, the Internet.

When used in a LAN networking environment, the computer 1001 isconnected to the LAN 1048 through a wire and/or wireless communicationnetwork interface or adaptor 1052. The adaptor 1052 can facilitate wireand/or wireless communications to the LAN 1048, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 1052.

When used in a WAN networking environment, the computer 1001 can includea modem 1054, or is connected to a communications server on the WAN1050, or has other means for establishing communications over the WAN1050, such as by way of the Internet. The modem 1054, which can beinternal or external and a wire and/or wireless device, connects to thesystem bus 1006 via the input device interface 1040. In a networkedenvironment, program modules depicted relative to the computer 1001, orportions thereof, can be stored in the remote memory/storage device1046. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1001 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.13 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and Bluetooth™ wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.13x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

FIG. 11 is a block diagram depicting an exemplary communicationsarchitecture 1100 suitable for implementing various embodiments aspreviously described. The communications architecture 1100 includesvarious common communications elements, such as a transmitter, receiver,transceiver, radio, network interface, baseband processor, antenna,amplifiers, filters, power supplies, and so forth. The embodiments,however, are not limited to implementation by the communicationsarchitecture 1100.

As shown in FIG. 11, the communications architecture 1100 includes oneor more clients 1102 and servers 1104. The clients 1102 may implementthe client device 510. The servers 1104 may implement the server device526. The clients 1102 and the servers 1104 are operatively connected toone or more respective client data stores 1106 and server data stores1108 that can be employed to store information local to the respectiveclients 1102 and servers 1104, such as cookies and/or associatedcontextual information.

The clients 1102 and the servers 1104 may communicate informationbetween each other using a communication framework 1110. Thecommunications framework 1110 may implement any well-knowncommunications techniques and protocols. The communications framework1110 may be implemented as a packet-switched network (e.g., publicnetworks such as the Internet, private networks such as an enterpriseintranet, and so forth), a circuit-switched network (e.g., the publicswitched telephone network), or a combination of a packet-switchednetwork and a circuit-switched network (with suitable gateways andtranslators).

The communications framework 1110 may implement various networkinterfaces arranged to accept, communicate, and connect to acommunications network. A network interface may be regarded as aspecialized form of an input output interface. Network interfaces mayemploy connection protocols including without limitation direct connect,Ethernet (e.g., thick, thin, twisted pair 10/100/1000 Base T, and thelike), token ring, wireless network interfaces, cellular networkinterfaces, IEEE 802.11a-x network interfaces, IEEE 802.16 networkinterfaces, IEEE 802.20 network interfaces, and the like. Further,multiple network interfaces may be used to engage with variouscommunications network types. For example, multiple network interfacesmay be employed to allow for the communication over broadcast,multicast, and unicast networks. Should processing requirements dictatea greater amount speed and capacity, distributed network controllerarchitectures may similarly be employed to pool, load balance, andotherwise increase the communicative bandwidth required by clients 1102and the servers 1104. A communications network may be any one and thecombination of wired and/or wireless networks including withoutlimitation a direct interconnection, a secured custom connection, aprivate network (e.g., an enterprise intranet), a public network (e.g.,the Internet), a Personal Area Network (PAN), a Local Area Network(LAN), a Metropolitan Area Network (MAN), an Operating Missions as Nodeson the Internet (OMNI), a Wide Area Network (WAN), a wireless network, acellular network, and other communications networks.

FIG. 12 illustrates an embodiment of a device 1200 for use in amulticarrier OFDM system, such as the messaging system 500. The device1200 may implement, for example, software components 1202 as describedwith reference to the messaging component logic 600, the intentdetermination logic 700, and the group selection logic 800. The device1200 may also implement a logic circuit 1204. The logic circuit 1204 mayinclude physical circuits to perform operations described for themessaging system 500. As shown in FIG. 12, device 1200 may include aradio interface 1206, baseband circuitry 1208, and a computing platform1210, although embodiments are not limited to this configuration.

The device 1200 may implement some or all of the structure and/oroperations for the messaging system 500 and/or logic circuit 1204 in asingle computing entity, such as entirely within a single device.Alternatively, the device 1200 may distribute portions of the structureand/or operations for the messaging system 500 and/or logic circuit 1204across multiple computing entities using a distributed systemarchitecture, such as a client-server architecture, a 3-tierarchitecture, an N-tier architecture, a tightly-coupled or clusteredarchitecture, a peer-to-peer architecture, a master-slave architecture,a shared database architecture, and other types of distributed systems.The embodiments are not limited in this context.

In one embodiment, the radio interface 1206 may include a component orcombination of components adapted for transmitting and/or receivingsingle carrier or multicarrier modulated signals (e.g., includingcomplementary code keying (CCK) and/or orthogonal frequency divisionmultiplexing (OFDM) symbols) although the embodiments are not limited toany specific over-the-air interface or modulation scheme. The radiointerface 1206 may include, for example, a receiver 1212, a transmitter1214 and/or a frequency synthesizer 1216. The radio interface 1206 mayinclude bias controls, a crystal oscillator and/or one or more antennas1218. In another embodiment, the radio interface 1206 may use externalvoltage-controlled oscillators (VCOs), surface acoustic wave filters,intermediate frequency (IF) filters and/or RF filters, as desired. Dueto the variety of potential RF interface designs an expansivedescription thereof is omitted.

The baseband circuitry 1208 may communicate with the radio interface1206 to process receive and/or transmit signals and may include, forexample, an analog-to-digital converter 1220 for down convertingreceived signals, and a digital-to-analog converter 1222 forup-converting signals for transmission. Further, the baseband circuitry1208 may include a baseband or physical layer (PHY) processing circuit1224 for PHY link layer processing of respective receive/transmitsignals. The baseband circuitry 1208 may include, for example, aprocessing circuit 1226 for medium access control (MAC)/data link layerprocessing. The baseband circuitry 1208 may include a memory controller1228 for communicating with the processing circuit 1226 and/or acomputing platform 1210, for example, via one or more interfaces 1230.

In some embodiments, the PHY processing circuit 1224 may include a frameconstruction and/or detection module, in combination with additionalcircuitry such as a buffer memory, to construct and/or deconstructcommunication frames, such as radio frames. Alternatively or inaddition, the MAC processing circuit 1226 may share processing forcertain of these functions or perform these processes independent of thePHY processing circuit 1224. In some embodiments, MAC and PHY processingmay be integrated into a single circuit.

The computing platform 1210 may provide computing functionality for thedevice 1200. As shown, the computing platform 1210 may include aprocessing component 1232. In addition to, or alternatively of, thebaseband circuitry 1208, the device 1200 may execute processingoperations or logic for the messaging system 500 and logic circuit 1204using the processing component 1232. The processing component 1232(and/or the PHY 1224 and/or MAC 1226) may comprise various hardwareelements, software elements, or a combination of both. Examples ofhardware elements may include devices, logic devices, components,processors, microprocessors, circuits, processor circuits, circuitelements (e.g., transistors, resistors, capacitors, inductors, and soforth), integrated circuits, application specific integrated circuits(ASIC), programmable logic devices (PLD), digital signal processors(DSP), field programmable gate array (FPGA), memory units, logic gates,registers, semiconductor device, chips, microchips, chip sets, and soforth. Examples of software elements may include software components,programs, applications, computer programs, application programs, systemprograms, software development programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints, as desired for a givenimplementation.

The computing platform 1210 may further include other platformcomponents 1234. Other platform components 1234 include common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components (e.g., digital displays), powersupplies, and so forth. Examples of memory units may include withoutlimitation various types of computer readable and machine readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information.

The device 1200 may be, for example, an ultra-mobile device, a mobiledevice, a fixed device, a machine-to-machine (M2M) device, a personaldigital assistant (PDA), a mobile computing device, a smart phone, atelephone, a digital telephone, a cellular telephone, user equipment,eBook readers, a handset, a one-way pager, a two-way pager, a messagingdevice, a computer, a personal computer (PC), a desktop computer, alaptop computer, a notebook computer, a netbook computer, a handheldcomputer, a tablet computer, a server, a server array or server farm, aweb server, a network server, an Internet server, a work station, amini-computer, a main frame computer, a supercomputer, a networkappliance, a web appliance, a distributed computing system,multiprocessor systems, processor-based systems, consumer electronics,programmable consumer electronics, game devices, television, digitaltelevision, set top box, wireless access point, base station, node B,evolved node B (eNB), subscriber station, mobile subscriber center,radio network controller, router, hub, gateway, bridge, switch, machine,or combination thereof. Accordingly, functions and/or specificconfigurations of the device 1200 described herein, may be included oromitted in various embodiments of the device 1200, as suitably desired.In some embodiments, the device 1200 may be configured to be compatiblewith protocols and frequencies associated one or more of the 3GPP LTESpecifications and/or IEEE 1402.16 Standards for WMANs, and/or otherbroadband wireless networks, cited herein, although the embodiments arenot limited in this respect.

Embodiments of device 1200 may be implemented using single input singleoutput (SISO) architectures. However, certain implementations mayinclude multiple antennas (e.g., antennas 1218) for transmission and/orreception using adaptive antenna techniques for beamforming or spatialdivision multiple access (SDMA) and/or using MIMO communicationtechniques.

The components and features of the device 1200 may be implemented usingany combination of discrete circuitry, application specific integratedcircuits (ASICs), logic gates and/or single chip architectures. Further,the features of the device 1200 may be implemented usingmicrocontrollers, programmable logic arrays and/or microprocessors orany combination of the foregoing where suitably appropriate. It is notedthat hardware, firmware and/or software elements may be collectively orindividually referred to herein as “logic” or “circuit.”

It will be appreciated that the exemplary device 1200 shown in the blockdiagram of FIG. 12 may represent one functionally descriptive example ofmany potential implementations. Accordingly, division, omission orinclusion of block functions depicted in the accompanying figures doesnot infer that the hardware components, circuits, software and/orelements for implementing these functions would be necessarily bedivided, omitted, or included in embodiments.

At least one computer-readable storage medium 1236 may includeinstructions that, when executed, cause a system to perform any of thecomputer-implemented methods described herein.

General Notes on Terminology

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Moreover, unless otherwise noted the features described above arerecognized to be usable together in any combination. Thus, any featuresdiscussed separately may be employed in combination with each otherunless it is noted that the features are incompatible with each other.

With general reference to notations and nomenclature used herein, thedetailed descriptions herein may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein, which form part of one or more embodiments.Rather, the operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers or similar devices.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. These terms are notnecessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for therequired purpose or it may comprise a general purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposemachines may be used with programs written in accordance with theteachings herein, or it may prove convenient to construct morespecialized apparatus to perform the required method steps. The requiredstructure for a variety of these machines will appear from thedescription given.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments require more features than are expressly recited in eachclaim. Rather, as the following claims reflect, inventive subject matterlies in less than all features of a single disclosed embodiment. Thusthe following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment. In the appended claims, the terms “including” and “in which”are used as the plain-English equivalents of the respective terms“comprising” and “wherein,” respectively. Moreover, the terms “first,”“second,” “third,” and so forth, are used merely as labels, and are notintended to impose numerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

1. A method, comprising: identifying a first module and a second modulefor presentation in an inbox interface for a messaging service, thefirst module and the second module providing access to features of themessaging service distinct from message or thread display features;determining a ranked order for the first module and the second module;and presenting the first module and the second module in the rankedorder after a first subset of messages from a set of messages presentedin the inbox interface.
 2. The method of claim 1, the ranked order beingdetermined based on at least one of historical interaction with themessaging service by a first user associated with the inbox interface orhistorical interactions with the messaging service by a user base of themessaging service.
 3. The method of claim 1, the ranked order beingdetermined at least in part based on a value of the first module and thesecond module to the messaging service.
 4. The method of claim 1,further comprising altering the ranked order based on content containedwithin the first module.
 5. The method of claim 1, further comprisingarranging content within the first module in an intra-module rankedorder.
 6. The method of claim 5, the intra-module ranked order beingdetermined by the first module.
 7. The method of claim 5, theintra-module ranked order being determined based on at least one of arecency of the content, an importance of the content to a user, or anaffinity for the content by the user.
 8. A non-transitorycomputer-readable medium storing instructions configured to cause one ormore processors to: identify a first module and a second module forpresentation in an inbox interface for a messaging service, the firstmodule and the second module providing access to features of themessaging service distinct from message or thread display features;determine a ranked order for the first module and the second module; andpresent the first module and the second module in the ranked order aftera first subset of messages from a set of messages presented in the inboxinterface.
 9. The medium of claim 8, the ranked order being determinedbased on at least one of historical interaction with the messagingservice by a first user associated with the inbox interface orhistorical interactions with the messaging service by a user base of themessaging service.
 10. The medium of claim 8, the ranked order beingdetermined at least in part based on a value of the first module and thesecond module to the messaging service.
 11. The medium of claim 8,further storing instructions for altering the ranked order based oncontent contained within the first module.
 12. The medium of claim 8,further storing instructions for arranging content within the firstmodule in an intra-module ranked order.
 13. The medium of claim 12, theintra-module ranked order being determined by the first module.
 14. Themedium of claim 12, the intra-module ranked order being determined basedon at least one of a recency of the content, an importance of thecontent to a user, or an affinity for the content by the user.
 15. Anapparatus comprising: a non-transitory computer-readable medium storinga messaging application for connecting to a messaging service; and aprocessing component configured to: identify a first module and a secondmodule for presentation in an inbox interface for the messaging service,the first module and the second module providing access to features ofthe messaging service distinct from message or thread display features;determine a ranked order for the first module and the second module; andpresent the first module and the second module in the ranked order aftera first subset of messages from a set of messages presented in the inboxinterface.
 16. The apparatus of claim 15, the ranked order beingdetermined based on at least one of historical interaction with themessaging service by a first user associated with the inbox interface orhistorical interactions with the messaging service by a user base of themessaging service.
 17. The apparatus of claim 15, the ranked order beingdetermined at least in part based on a value of the first module and thesecond module to the messaging service.
 18. The apparatus of claim 15,the processing component further configured to alter the ranked orderbased on content contained within the first module.
 19. The apparatus ofclaim 15, the processing component further configured to arrange contentwithin the first module in an intra-module ranked order.
 20. Theapparatus of claim 19, the intra-module ranked order being determinedbased on at least one of a recency of the content, an importance of thecontent to a user, or an affinity for the content by the user.